Said It Here

Why is NetSuite API development so inconsistent?

NetSuite's poorly designed architecture features unpredictable behavior where methods that work in standard REST fail in Restlets, and patterns used for one record type don't apply to another. This lack of standardization forces developers to abandon modern tools like ORMs and manually troubleshoot arbitrary quirks for basic tasks like creating invoices or credit memos.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    Writing custom REST APIs, SuiteQL, and Restlets directly
  2. 2
    Using custom user events to handle specific quirks like shipping taxes
  3. 3
    Using the built-in script debugger instead of an IDE
  4. 4
    map everything out and have graceful error handling

In their words

Unedited, most upvoted first, each linked to the thread it came from.

“Which brings me to my irritation with NetSuite - it's the worst designed product I have ever worked with. Nothing about it makes any sense.”source ↗

“What works in REST doesn't work in Restlets and vice-versa.”source ↗

“You can't guarantee what works for creating a new invoice will work for creating a credit memo even in a Restlet.”source ↗

EarthCivil7696 · r/Netsuite · 78 upvotes

“The fact that I'm writing these restlets instead of using an ORM is one of the most frustrating things I've encountered in a long time.”source ↗

xdevnullx · r/Netsuite · 6 upvotes

“I get the source of your complaint, but this isn't something that's completely unheard of when you don't have full control of the backend.”source ↗

gforce360 · r/Netsuite

Where this came up

r/Netsuiteapi integrationdevelopmententerprise softwaresoftware engineering

People with this problem also raised