Scenario: I wanted to set a JE header field based on ANY line being tied to a Bank account. So, I created a custom list for a custom field on the JE. The field has a default value ("X)"). I then created a summary SS that captures any qualifying JEs. I then created a very simple workflow with that SS as the condition; it has one action for Set Field Value (to "Y") if the JE is in that search. I deployed all of this, and my users were getting the attached error. They were technically able to create entries, but they couldn't view them or edit them (and I could). Long story short, I was dumb - the SS was not public. Once I made it so, they have no issues. My question: how does any SuiteScript come into play here? How can I determine which script that error might have been caused by? I don't understand how the combination of customizations I built/deployed would have prevented them from viewing or editing anything, regardless of the Public status of the search.

look at workflow log for the applying records. for scripts, if something blows up, by default the script owner gets an email with detailed errors.