I'm setting a SO field in a client script but it's disappearing from the record, I added logs in the before and aftersubmit and I can see the value, so I'm not sure in what stage the value is being removed. Some roles edit the form later on and the client script runs again and the value sticks, so I think it has something to do with permissions, how can I further debug this?

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like the issue you're experiencing might be related to the permissions of the role that is executing the script. In NetSuite, client scripts perform searches and access data with the permissions of the current user role. If the role can't see the underlying searches or the values, it will look like no results, and you'll get fields set to blank. Here are some steps you can take to debug this issue: 1. Check the role permissions: Use the role with the missing values and attempt to find the field values in the UI to be sure that's the problem. If it is, you can either add role permissions, maybe update the records or fields to add it to the access list. 2. Use a Suitelet: If the issue is indeed related to permissions, you can use a Suitelet that runs as admin and have your client script call the suitelet to get the data it needs. 3. Check if the script is actually running: Make sure that the script is actually running when the record is being created or updated. You can do this by adding log statements in your script and checking the execution log. 4. Try making the change in afterSubmit: If the issue persists, you can try making the change in the afterSubmit event. However, this might have performance implications as you would need to load the record again and submit it. 5. Check for interfering workflows: In some cases, the issue might be caused by an interfering workflow. Make sure that there are no workflows that are modifying the same field. Remember to always test your changes in a sandbox environment before deploying them to production. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******