After years, why is the SuiteScript 1.0 version still necessary?

Integrator.io
,
1

Related to Invalid NS API function name in debug logs - Serious bug or just logging bug?... I didn't want this to get buried as a reply to that topic so I'm starting this one.

I've been struggling with an Item Fulfillment for many hours. Opened a NetSuite support case (because the Celigo error message suggests as much) and finally met with the brilliant, esteemed @davidgollom :grinning_face:

So... the error from the Import step was:

Failed to create, update/transform record because null Possible reasons include > Something went wrong on NetSuite side. > You might have specified an invalid field value for a field. > You may have submitted an invalid record. Please consult NetSuite Support with NLAPI calls obtained from NetSuite Connection Debugger.

Dave asked "Did you try a 1.0 version?? Shouldn't still need to do that, but in these weird cases it sometimes works." Well, Dave... it does work and I would love to know why!

Celigo, can you help us/me understand why this is still needed? I know this "workaround" has been a possible solution for years, here's a thread from August 2023. Luckily the SuiteApp 1.0 version works and we don't need to use the SuiteBundler version. Is there a real NetSuite difference in the APIs that make this workaround a valid option, or is this a case of "we just haven't fixed it yet"?

2

Hello Steve,

Thank you for sharing this community thread and for raising your concerns regarding the continued use of SuiteScript 1.0 within NetSuite and Celigo integrations.

While NetSuite has introduced newer scripting frameworks over the years, the older SuiteScript 1.0 framework is still officially supported and continues to be widely used in many existing integrations and solutions.

In some situations—especially involving more complex transaction processing—the newer framework can occasionally encounter platform-related errors that are difficult to diagnose and may interrupt the integration process. In this case, we observed this type of issue during processing.

To restore stability and ensure your data continued syncing properly, we utilized the SuiteScript 1.0 framework as an alternative approach. This allowed us to:

  • Avoid the system errors that were interrupting the process.

  • Ensure your data continued processing correctly and reliably.

  • Restore the integration to normal operation without further delays.

Please rest assured that this is a known and commonly accepted approach for handling these types of NetSuite platform limitations. It will not negatively impact the security, stability, or long-term performance of your integration.

We will continue monitoring the integration to ensure everything remains stable moving forward. If you have any additional questions or concerns, please feel free to let us know.