I'm trying to programmatically replicate the action of editing a Cash Sale record, selecting a line from the billable expenses (

expcost

) sublist, and marking the

apply

checkbox in SuiteScript. I've attempted this in

afterSubmit

,

beforeSubmit

, and other User Event script stages, but I'm encountering errors or the script fails silently. Is there a specific approach or best practice for reliably modifying sublist fields, especially for fields like

apply

in

expcost

, or are there known limitations with this sublist in SuiteScript?

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that you are encountering a common issue with SuiteScript when trying to modify sublist fields, especially the

apply

checkbox in the

expcost

sublist. In SuiteScript, you cannot alter values in a

beforeLoad

User Event script, which may be causing the issue you're experiencing. Instead, you might want to consider using an

afterSubmit

User Event script. This is because the

afterSubmit

event occurs after the record is committed to the database, allowing you to modify sublist fields without encountering the same restrictions. However, please note that there are some limitations when working with sublist fields in SuiteScript. For instance, if a sublist is not visible on the form that your script is interacting with, the script may fail as it cannot see the fields. In such cases, you might need to ensure that the sublist is visible on the form, or consider using a different approach. In addition, when working with the expense sublist on expense reports, you might encounter issues if the expense report includes certain types of lines. For example, if the expense report includes a line with a value of 0.00, or a line with a negative sum, you might encounter a generic SuiteScript error. In such cases, you might want to consider using dynamic mode, as this might provide a more helpful error message. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******