Getting unexpected error when creating an Estimate, but no script logs are recorded anywhere saying unexpected error. How do I find out what's causing the unexpected error?

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** The

UNEXPECTED_ERROR

in NetSuite typically means that there is no specific information available about the error. It's a generic error message that can be triggered by a variety of issues. Here are some steps you can take to troubleshoot this issue: 1. Check Scripted Records: Look for any User Events and Workflows that are deployed on the record you're trying to create. Try disabling these one by one to see if the error persists. This can help you narrow down the source of the issue. 2. Check the Context: If the record is being created from a RESTlet or a User Event Script, it might not trigger certain workflows or other User Event Scripts that are deployed on the same record type. You can refer to the NetSuite Help Center's guide on [How User Events are Executed](https://system.na0.netsuite.com/app/help/helpcenter.nl?fid=section_1512409310.html) for more information. As a workaround, you can use the [N/workflow Module](https://system.na0.netsuite.com/app/help/helpcenter.nl?fid=section_4341725558.html). 3. Check Your Script: Make sure that you're using the correct case for record types, as they are case sensitive in SuiteScript. For example, use

record.Type.ESTIMATE

instead of

record.type.estimate

. 4. Check Your Deployment: Sometimes, if you only upload the script file, NetSuite might still use a cached version. Try re-deploying your script or editing and saving the script deployment to ensure that the latest version is being used. 5. Check Your Record IDs: Make sure that you're using the correct internal ID for the record. For example, if you're working with an estimate, ensure that you're using the internal ID, not the transaction ID. Remember to always test your scripts in a sandbox environment before deploying them in production to avoid any unexpected issues.