โ07-11-2017 06:59 AM
Hello. In building out an integration from Salesforce to NetSuite Iโve not been able to find a way to update a value from Salesforce to a list value in NetSuite by leveraging the text. It seems the NS Update and Upsert Snaps want you to provide the internalId of the list value rather than resolving the internal id from the actual text value.
E.g. in SFDC we have a subsidiary = โAcme, Inc.โ and in NetSuite on the account record there is a Subsidiary list with the same exact value = โAcme, Inc.โ. If I try and update the โAcme, Inc.โ to the Subsidiary value in NS the snap fails. It only works when I provide the ID associated to the list item (letโs say in NS the Internal Id of the value โAcme, Inc.โ = 123).
My current workaround is to export the list of values from NS and put that into a CSV (so it has the values and the internal id). But now that means for every list I need a mapping file and then a join on the text values just to get the internal id? There must be a better wayโฆ anyone else experience this?
โ07-12-2017 02:21 AM
You can make a search in NetSuite(NetSuite search snap), to search the subsidiary based on name and NetSuite will return itโs internal id which you can later map it to successfully insert a value for subsidiary field.
โ07-12-2017 06:29 AM
thanks but isnโt the NetSuite search snap meant to search actual records? in this case I am looking to get all possible values on a List (a picklist on the customer object in NetSuite). on the list there are internal ids associated to each dropdown value (all possible values which may not yet be on some records).
โ07-12-2017 07:30 AM
If you select the subsidiary object in the NetSuite search snap and search based on the name that you have, it will return the internal id of that specific subsidiary. Because the object subsidiary in NetSuite is actually the list of subsidiaries that you are mentioning.
โ04-24-2018 06:21 AM
Hi Matt, I know this is an older question, but I also build integrations for our company between Salesforce and NetSuite. Doing a NS search and then using the internal IDs from that is an option, but in my opinion it isnโt very efficient.
Another way of handling this is to use a Conditional snap and read the value from SF (i.e. Acme) and map it to the internal ID that NS is expecting (i.e. 123). Your NS admin should be able to provide the internal IDs for all lists. Also, internal IDs do not change in NS, so you donโt have to worry about constantly maintaining themโฆ unless a new value is added, which isnโt a big deal to add it.
Lastly, in SF, you can edit the API name of a picklist value. Assuming you donโt have any other integrations that may be impacted by this, you can always go to the picklist value (in this example, Acme) and edit the API name to be โ123โ. Then in your pipeline, you wonโt need a Conditional snap at all - instead it will just map directly over to NS as โ123โ.
Hope this helps!