This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

biggest issue I can see is lack of queuing and no central place for error handling if you have multiple script based integrations from different vendors.

What type of concurrency do you need? Unless you have a heavy load the restlets should be able to handle it.

few hundred JSON messages per minute maybe

some for receipts, some for fulfilments, some for updating specific fields on various fulfilment and SO records

The sender won't be re-sending anything that fails either so it's good to hold the failed attempts  in a queue so they can be retried later or after adjustments have been made to fix whatever issue caused the failure.

I'm getting annoyed at all the different integrations doing their own thing and handling errors in their own way. I want everything going through a central system so there's one place and one way to manage everything

If the login fails there is no way to trap that, it's lost

The login won't fail, that's very unlikely

it's more likely a user error will happen which might stop a record from saving or similar

I have an API Log that I use (and sell) for all of my integrations. It traps the calls in and out when used. It also has an internal retry button.

Yeah, that's what's missing here. Each integration has it's own way of doing that because NS doesn't prescribe anything

I'm really not a fan of point to point integration. I saw one customer doing all integration through Kafka - it was very nice!

I personally like the p2p integrations for security reasons.

I can't see how p2p is more secure than middleware

I guess you're removing one vector of attack but that's all

Because your data is not sent and stored on a 3rd party server

Does your solution hold onto every failed attempt so the JSON / XML can be retried?

Especially when it comes to transactions and banking

well - you can host your ETL on your own infrastrucutre

And yes, my logs keep everything. I suggest doing a purge after so long so that it's not eating up memory/space in the account.

you're effectively building an ETL tool in NetSuite then

I like that idea becasue it means you can remove reliance on IPASS solutions like Celigo and Boomi

I guess buiness users can't easily integrate or map records with that solution though

and everything you do now requires suitescript

Kafka does have some very nice features for handling these kind of scenarios. Though it might be overkill...

Before we (Celigo) built <http://integrator.io|integrator.io>, which is an iPaaS, our integration solution was exactly this :point_down: . But it’s a lot of effort to build and you end up with a solution that’s captive to NetSuite integrations by design. <https://netsuiteprofessionals.slack.com/archives/C29HQS63G/p1602084153435300?thread_ts=1602076583.424400&amp;cid=C29HQS63G>