AnsweredAssumed Answered

Updating Netsuite API 2010.2 to 2017.2 ?

Question asked by 53567878 on Jun 21, 2018
Latest reply on Jul 9, 2018 by Sjaak Overgaauw

We have a large number of processes built that push and pull data into Netsuite (I am guessing 30 process with many many mappings). We are still using Netsuite API version 2010.2, which unfortunately does not support upsert.

 

To get around the lack of upsert, we have a number of processes which search NS with one connector, then route to an update or create based on the search results. It's very clunky, but has been functional... until now.

 

We now have a volume of processes such that many are erroring based on the 'one connection at a time' issue with Netusite.

 

To fix this we would like to update our processes to use Netsuite API 2017.2, however, it seems like doing so has to be done all at once because we have a limited number of connectors. Will we have to remap everything if we update our API versions? Is there any way around rebuilding everything (can we simply replace the old profiles when update API and not have issues? Has anybody tried this before?

Outcomes