When a third party integration is sending an update to a field that we want to prevent what's the best way to prevent that field from being updated? Our HR System is sending employee record data, and part of their update includes the entity id on the record, which changes the entity id from the expected {lastname}, {firstname} format to a numerical value. We have tried creating a new custom form that was then set as preferred for the role used by the integration, and then deploying a custom client script to the form specifically, but that had no impact, the integration doesn't seem to use that form. We then deployed the client script at the record level and updates still came through with a numerical value. Right now we have a map reduce that checks for, and corrects these issues, but we would prefer to set things up so that the issues don't happen. Is this something we can control within NetSuite or will I need to reach out to the third party integration people? If this question is better asked in a different channel I apologize, but this seems like a good place for it.

client script had no chance of working

That makes sense then, I thought I had seen an instance where that approach was valid. I'll try the user event, thanks.

you might be able to avoid a script if you use the limitations for Fields in SOAP Web Services

hmm, so it looks like: "If a standard field is set to NOT show in the UI, it is not settable through SOAP web services, either. If you try to set such a field through SOAP web services, an error message is returned." but I wouldn't want an error to be returned to the third party system either, I just don't want their system changing the entityid

Maybe User Event before submit compare the field value on oldRecord to newRecord and revert the field back if it's been changed maybe? (may hav eto consider it going from blank to it's initial value so as to not lose that) Have it run only for the context you're interested in so it doesn't change if you legitimately want to, say through the UI.