It’s Halloween, and there are dozens of things that will scare your pants off this week – the bed-sheet ghosts hanging on the front porch of the houses in your street, the jack o’lanterns that remind you of that great aunt with too much makeup and always smelt of mothballs and bourbon… not to mention the thought of getting healthy snacks in your trick or treat bag *shudder*.
But there’s one thing you shouldn’t be afraid of this year and that’s your NetSuite integration options. Let’s face it though, that’s easier said than done given there are a number choices and you don’t really have the time to look into everything (you’re too busy making your costume, right?).
So, with that in mind, let’s take away the mystery surrounding your NetSuite integrations options.
SuiteScript API (Integration out from NetSuite)
SuiteScript is a popular option when integrating NetSuite with applications such as Pardot (which is just one example of a SuiteScript API connection). In the case of Pardot, SuiteScript allows you to pull data from email marketing and other marketing campaigns from Pardot even though the marketing-automation platform doesn’t offer complete integration with NetSuite out of the box. This can be a game changer and so it’s important to keep it up your sleeve if you want to get the most out of a tool like Pardot when you’ve got NetSuite working nicely for you
RESTLet (Integration in/out to/from NetSuite)
RESTlet may move faster than a speeding bullet but unfortunately falls short of being as powerful as a locomotive.
The beauty of RESTlet lies in the fact that it’s quick and returns data in a flash, especially compared to other options that you’ll soon find out about. That means limited downtime and disruption to the application.
Where RESTlets stumble a bit is in the areas of practicality and functionality. RESTlets are nimble and quick, but can become fragile when attempting to process large amounts of data. In truth, RESTlets maximum data size of 10MB for both input and output can cause problems if you’re not careful.
Public Suitelet (Integration in/out to/from NetSuite)
I’m not going to sit here and tell you this is a good option, but I will explain what it is.
Suitelet is an extension of the SuiteScript API that gives developers the ability to build custom NetSuite pages, as well as backend logic. So, now we have this out of the way…
DON’T USE PUBLIC SUITELET! NOPE. DON’T. JUST DON’T.
Why? It’s PUBLIC! Basically, it’s not secure and if that URL gets out you’ll be opening the floodgates and welcoming anyone who wants to access it and re-program. We good? Ok…
Web Services (Integration into NetSuite)
Web Services is another integration option worth considering, mainly because it’s one that can handle huge amounts of data, unlike the RESTlet option. However, there are two major drawbacks in the Web Services option, so let me put them on the table:
- One user per license connection, meaning it gets super tedious because you can’t have multiple web service connections with the one licence. There are ways around this but it can get pricey.
- Your dev team needs to be PROS. And I mean way on top of their game. PRO TIP: Call us!
