This topic contains 4 replies, has 0 voices, and was last updated by pcutler 7 years, 1 month ago.
-
AuthorPosts
-
September 28, 2017 at 10:01 am #21396
andreea@melimelo.comI'm trying to approve a sales order and I'm getting the attached error.
Please advise what I need to do.
This is a cached copy. Click here to see the original post. -
September 28, 2017 at 11:48 am #21397
pcutlerThis is do to custom scripting in your account. If you are not a developer, you will have to reach out to the developer who maintains the custom scripts in your account.
If you are a developer, navigate to CUSTOMIZATION > SCRIPTING > SCRIPTED RECORDS (menus may vary by role) and select "Sales Order." One of the scripts on the "User Event Scripts" tab is causing this error. You can navigate to each script record and check the execution log tab for this error to see which one. The script needs to be edited to be more efficient or undeployed entirely.
-
September 28, 2017 at 2:21 pm #21398
erictgrubaughAlternatively, use the Script Execution Logs UI to search for the Error message and find which Script is triggering it: Customization > Scripting > Script Execution Logs; try filtering by Log Level "Error" and the most recent date you saw the error message.
-
September 29, 2017 at 9:42 am #21399
andreea@melimelo.comThank you for your replies. But I couldn't see any error script similar with the one in question in the Log. Is there anything else I can do in this case?
-
September 29, 2017 at 9:49 am #21400
pcutlerAs far as fixing the error, it sounds like you're going to have to grant someone familiar with SuiteScript access to your account to track it down for you.
However, if this is the only order with the problem, and you just want to approve this one order, you can update the status via CSV import and uncheck the checkbox for running scripts (will need to expand the additional settings on the second page of the wizard). This will bypass any business logic that developers have implemented in your account.
-
AuthorPosts
You must be logged in to reply to this topic.