Does anyone know how to determine which application is configured to set external ids? NetSuite help says "To maintain data integrity, only a single integrated application can set and update external ID values for each record type." But I see no guidance on where to see or change this.

perhaps look at the system notes on a record you know has had externalid set? It's not really true to say it must be only one system that sets externalid - the salient point is that externalid is an indexed field with a 'unique' constraint

We have an integration that should be setting external ids. For some reason the change is not sticking. No error. So looking into if there is a restriction I can point the business too.

an enforcement of what?

Single integration application setting external ids.

I'm not aware of NS having a restriction at that level

Fun. So my next step is going to be having NS support tell me what their documentation means when it says "To maintain data integrity, only a single integrated application can set and update external ID values for each record type." The business wants to know how to see which application is set to update external ids based on that language.

Did you try looking at system notes - I can't remember if SOAP updates reflect the proper user, but if it does that's a viable idea

Will dig in to the notes. Looking at SAFE now.

yeah this is just a NS recommendation and its absolutely NOT enforced. you can have two systems set externalids on a record type if they don't touch the same records, you just have to ensure they have naming conventions that means they won't have conflicts. so you have each system start the external id with a 3 letter system abbreviation or something.

That’s annoying. I took the docs at their word and forced all systems which set external ids to use the same integration. .

I mean it probably is a best practice 🙂

I don't like it. One integration application per integration for me. I want to control them all.

you can also just use a custom field as a pseudo external id, you don't get the enforced uniqueness, but if you manually search for that field value you can update instead of creating dupes

Indeed, it's the uniqueness and stability of that field value that is important. If you have a single master for say, Customers that is the single source of truth for customer ids, it shouldn't matter if you have 15 systems integrating to NS as long as they all refer to that same single customer id for a given customer.