Why N/search ResultSet.each() is not executing on afterSubmit()?

AI generated answer (using internal Slack threads):

The

N/search ResultSet.each()

function may not be executing in the

afterSubmit()

due to a few reasons: 1. Return Value: In the

each

function, you need to ensure that you are returning

true

at the end of the function. If you do not return anything, it is treated as

false

and the function will not continue to the next result. This is a common issue and can cause the function to only run once even if there are multiple results. 2. Permissions: If you are using SuiteQL in an

afterSubmit

UserEvent script, you might encounter issues if the role you're using does not have access to the custom record that you're referencing. Even if you're running as an administrator, you need to ensure that the necessary permissions are in place. 3. Code Errors: There might be errors in your JavaScript code. For example, failing to properly insert the required space between the last SELECT column name and the FROM statement in a SuiteQL query can cause an error. 4. Record Existence: If the data you're trying to access with

ResultSet.each()

requires the record to already exist, then you might encounter issues if you're trying to run this in an

afterSubmit

context. In such cases, you might need to consider moving the logic to a

beforeSubmit

context or calling a scheduled script. Remember,

afterSubmit

is generally not the best place to modify the created sales order as it causes the sales order to be saved twice, which can be detrimental to performance. If possible, consider moving the logic to

beforeSubmit

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