This topic contains 2 replies, has 0 voices, and was last updated by HJMkreminski 7 years, 8 months ago.
-
AuthorPosts
-
HJMkreminski- Contributions: 0
- Level 1
- ☆
Sometime in the last 24 hours several of our scripts have had the postSourcing function added to their Post Sourcing Function within the script.
We do not have a postsourcing function so this caused our script to fail.
Was this something that came as part of a thursday release? Do you know what would have caused this?
It was not added by one of us and I have since removed it from the erroring scripts, but I will need to look at all of oru script to ensure that the problem doesn’t exist there as well.
The sandbox did not have these changes .
This is a cached copy. Click here to see the original post. -
Olivier Gagnon NC- Contributions: 0
- Level 1
- ☆
Is this for Suitescript 1.0 or 2.0?
And do you mean that your script FILE was modified, or the script record in NS was modified and a function written into the postSourcing trigger? I would assume the latter – if so, what was the name of the function inserted?
Did you check History/System Notes to see if anything was logged?
-
HJMkreminski- Contributions: 0
- Level 1
- ☆
Suitescript 1.0 the script record in NetSuite was modified with the value postSourcing added to the trigger. Yes there was nothing in the History/Notes
-
AuthorPosts
You must be logged in to reply to this topic.