Export "Search internal ID" field - safe to use Script ID?

[steveklett]

Hello,

Using internal IDs (IIDs) for a private saved search can create issues when a NetSuite sandbox account is refreshed. Develop integration in sandbox with a search IID 1234, refresh SB and now search 1234 may point to something entirely different. - we're all familiar with the pitfalls of using IIDs in external systems and across account environments. This is why NetSuite finally added support for Script IDs (yay!)

OK, so in Integrator.io (IIO) we use private searches with script ids entered instead of IIDs and this works fine except we can't launch the search from the little icon - no sweat, we don't use that feature so don't care about losing it.

My question to Celigo and the community: Is this a safe practice? Is the fact that IIO will accept a string script ID a bug that will be fixed at some point or is it an undocumented or secret feature that will be safe in the future?

Regards,
Steve

[stephenbrandt]

Hi, @steveklett. Very impressive: you described this functionality almost exactly as did our engineering lead and NetSuite expert, who also recommended, “It is always a best practice to set your own ID for a saved search.”

The script ID feature was introduced specifically to support sandbox refreshes, when the internal ID changes. The script ID is safe to use – in production and sandbox – and would not be changed by NetSuite or integrator.io.

Unfortunately, NetSuite cannot open a saved search with just a script ID passed, so that launch button shortcut won’t work in this case.