This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

```                try {
                    newRecord.setText('shipmentStatus', 'In Transit');
                    log.debug('Status set');
                } catch (e) {
                    throw e;
                    log.debug('Cannot set', e);
                }```
The field name is incorrect but there is no error in the logs. there isn't even a log from the catch.

I would expect setting a value to an incorrect field name would throw an error.

image.png

Or would an incorrect field name count as undefined?

Incorrect isn't undefined. It'll just silently fail

If it throws an error, that can be caught and logged at least.

In a perfect world, all field names would be available as some sort of ENUM. Having unvalidated strings floating around just asks for mistakes to be made, especially in larger codebases.

Yeah, I have inherited a very large number of scripts. This is part of my review.

I've brought in coding standards which force the use of the internal ID in setValue()

umm set anything doesn't throw an error does it?  I doubt you'd get an error till you tried to save the record and write to db anyway

<@U9FNFCWRF> above that try is this beauty of a comment

// defensive try

To be fair to the dev that wrote this, I can't find the list/internal IDs for this field either. It's the shipmentstatus on the Inbound Shipment record which is a SuiteApp from NetSuite.

I guess they thought a setText was a quicker option to delivering something.

RE/TE (reverse engineering/trial and error)

Inbound Shipments aren't really a 'record' in the traditional NetSuite sense.  They're kind of a record/list hybrid.  A right royal pain to work with.