I can also run searches normally. But clicking to view/edit these…error. I haven’t made any changes myself recently, but NetSuite did perform maintenance 12/10 and I’m wondering if something there caused the fubar? I’ve found I can view some SO, and they all seem to have an old custom form saved with the record, but still an error if I click Edit on the record, also an error if I click the form in the custom transaction forms list to go right to that particular form to create a record. Not really seeing major difference between this form and a newer one I created that’s been my preferred form. I deployed a small UE script on SO/INV to see if those entry points run, and the

beforeLoad

does complete and logs debug statements. Can’t get to before/after submit of course, but it’s odd the

beforeLoad

executes and then boom, 500 server error. Not sure if this is related to 2025.1 maintenance prep and the 12/10 maintenance too, or maybe a feature I have enabled that now conflicts with some of these prep changes/maintenance? But I just haven’t made any account/feature changes recently, so this is an odd one. I’ve searched online for a while and haven’t come across anyone describing a similar experience, but wanted to throw out here in case anyone has encountered this and I’m not alone? And/or if anyone has any ideas on what might be causing the error that I’ve overlooked?

I cannot use SuiteScript in the browser console to laod/save an SO or INV. Results in an error. Even running a GET for an INV with Postman using the REST record API returns 500 server error. Very odd and out of nowhere.

These demo accounts come with a bunch of data and various features turned on. So my thought is I’ve hit some rare edge case of certain feature(s) enabled but the supporting config or records not implemented fully, or in a way that based on a recent update is now causing the server side error. For instance I was working with a client that had Multiple Shipping Routes turned on, and on a credit memo, you couldn’t change any field values because some js errors were thrown on page load. Upon looking at the console, the errors pointed me towards shipping and likely the multiple shipping routes feature — the client uses an integrated shipping application, and books the expenses in NetSuite etc as needed, but they never really fully set up shipping items and accounts etc, so apparently that feature was causing the headache because as soon as I disabled it, working with credit memos started working again fine, no js exception or errors on page load. I have a feeling it’s something similar to this in my account. The client’s issue started sort of out of the blue too — no feature changes or shipping config related changes had been made in a long time, but all of a sudden there was that issue. Perhaps from some sort of hotfix/scheduled maintenance tasks since it didn’t seem to be a consequence of anything they/I did in the account.

I’ve been poking away at this the last few days, figured a script could be a culprit but no. I also had Multiple Shipping Routes enabled in my account — but since I got it, I didn’t enable or set anything up, so figured I’d get that disabled since it was also a problem for my client out of the blue, but that didn’t fix it, and did require deleting some transactions before I could disable that as well. So, general cleanup. Removed some old bundles that were already installed for the account. Nada. But just now, looking at other enabled features, I disabled Gross Profit (Enable Features > Transactions tab > Sales section. And now the new SO form loads, invoices load, etc. Appears that was the issue. Since I didn’t enable that feature and haven’t configured anything related to it, the fact it was the issue out of the blue is frustrating but not completely surprising. I re-enabled it to confirm, and the errors returned. Disable it again, and working again. Is it a combo of that feature and others, so disabling a different (conflicting somehow?) feature fix the errors as well? I dunno. May dig deeper, but happy to seemingly get this resolved. Not sure anyone will read all this or it’ll be helpful to others, but if you run into a 500 error and it doesn’t seem connecting to any scripting, keep after it. Would be nice for a helpful error to be returned that points more to a bad item costing config, or what feature logic was running when the error throws, but just the always helpful “unexpected error” and 500 internal server response. 🤷