The code, and the connections

SuiteScript, SuiteTalk and the integrations on either side of NetSuite — from a NetSuite Certified Web Services Developer.

Accounts that have been live for for a significant length of time carry two kinds of technical debt: scripts nobody wants to touch, and integrations nobody fully documented.

Both are about to matter more. Oracle has published dates for retiring the authentication method and web services many of those integrations depend on, and for SuiteScript versions older than 2.1.

Talk about your integrations What Oracle is switching off

What the work covers

SuiteScript

New development in SuiteScript 2.1, and maintenance of what's already there in 1.0 and 2.0 — including the scripts everyone is afraid to delete.

SuiteTalk and RESTlets

SOAP/XML and REST web services, and RESTlets where a standard endpoint doesn't fit the shape of the data.

Authentication

Token-Based Authentication and OAuth 1.0 and 2.0, set up so an integration authenticates as exactly what it needs and nothing more.

SDF and deployment

SuiteCloud Development Framework projects and SuiteBundler, with customizations kept in source control rather than only in the account.

Data migration

Conversion and ETL through SuiteTalk, SuiteQL and CSV import, reconciled rather than just loaded.

Workflows, searches and templates

SuiteFlow, saved searches and SuiteAnalytics, and Advanced PDF/HTML templates for the documents customers actually see.

Integrations built, not just configured

  • Salesforce CRM and Salesforce Billing to NetSuite, including Advanced Revenue Management so ASC 606 schedules come out right on the NetSuite side.
  • Coupa to NetSuite, for purchasing and spend management. I'm a Coupa Certified Platform Consultant as well.
  • A standard NetSuite integration for a SaaS purchasing and AP automation vendor — designed, built and tested as a repeatable product integration using both SuiteTalk web services and RESTlets, rather than a one-off for a single customer.
  • Amazon Marketplace to NetSuite for a consumer electronics accessories retailer: sales orders, item fulfillments and Amazon fee journal entries through SuiteTalk, automating about 90% of what had been processed by hand.
  • Stripe payment processing, built as an application on AI Application Manager.

Where middleware or an iPaaS is already in place, I work with it. Where it isn't, I'll tell you whether you actually need one.

SuiteScript 1.0 migration

The one technical service with its own page, because it has its own tool.

Every custom script in the account is catalogued and scored for complexity and risk. Conversions to 2.1 come with a regression suite derived from the original 1.0 source, not from the conversion — so the tests check the new code against what the old code actually did.

The result is delivered as an SDF project in a pull request to your own repository, with the original scripts preserved alongside it. Nothing is written back to NetSuite by the tool; your developer reviews, tests in a sandbox and deploys.

How the migration works, and what it costs →

On TBA and SOAP

If your integrations still authenticate with Token-Based Authentication or call SOAP endpoints, the deadlines page sets out Oracle's dates and how to find out what's actually live in your account.

A packaged remediation service for TBA and SOAP isn't something I offer yet. Rebuilding or re-pointing a specific integration is ordinary integration work, and I'm glad to scope it.

Send me the integration nobody wants to own

What it connects, what it's supposed to do, and what it's actually doing. That's enough to start.

Get in touch