Hi Netsuite friends! We have a proper head-scratc...
# integrations
d
Hi Netsuite friends! We have a proper head-scratcher and I am hoping someone else has figured this out We currently push salesforce opportunities with Dell Boomi into Netsuite to create sales orders. The challenge we have encountered is in handling item groups or kits this way. • we can define an item group and add it to a sales order, but if there is any variation on the line items in the group at the salesforce end, we cannot define them when we send it through to Netsuite. EG in this scenario: item group 1 includes :2x of Item A1x of Item B In Salesforce the user has applied a discount and removed a quantity of 1 of item A. We can't figure out how to add the item group 1, change the quantity of item A, or the price of it. Has anyone figured this out? The main requirement is that we want to group these items into one line item for invoicing, so if there's a better route then let me know!
c
How would you do it directly in the netsuite UI?
d
in the UI you can freely edit the line items in an item group. You can add, remove or delete them
the challenge seems to be referencing an item group and defining its contents via the API (or in this case the API via Dell Boomi)
r
Create your custom restlet to create the sales order ? And call it from Salesforce ?
d
thanks guys, glad to hear that I'm not the only one finding them a challenge. @raghav that's something I'll look into. Right now we are just using the standard SOAP API through Boomi so will look into whether RESTlets might allow us more flexibility to develop our solution
b
We are handling group updates using a two step process. Our Salesforce integration creates the SO with the group items. On save, NetSuite adds the lines for group members and we populate a custom line field that stores a unique id field that both Salesforce and NetSuite can determine. The integration makes a second call to update pricing for any group member lines using the unique id field to identify the right lines. Sounds pretty similar to what you're trying to do.
d
Sorry I missed this @Ben Tanner, that sounds exactly like what we are trying to do. How are you populating that unique ID that allows the lookup if Netsuite is creating the line items on save?
b
When the integration adds the group item to the sales order it populates a custom column field with the SF quote line id. On save, a beforeSubmit script sets the unique id column field for each of the group member lines using that SF quote line id from the group item and the component item internal id. Our item records are mapped between the two systems so SF knows the NS internal id for each item. That means SF knows that same quote line id + item internal id combination and can then relate every quote line to a matching NS sales order line.
d
@Matt
thanks Ben! that's super useful
b
Hopefully the detail makes sense and it helps. Good luck!
d
it does! So if I understand correctly: • group added to netsuite with a unique ID added to a field by boomi/mulesoft/whatever • Netsuite populates group • Netsuite before save script applies the above ID with the item ID appended to the included line items (how are you identifying these in the script? or are you doing it for ALL line items whether in a group or not?) • Look up items with the Unique ID&itemID you are expecting to find, then update their details I think it's just that one question really with the script. How do you stop it from applying the ID+itemID to that extra field for any non-group item, or if you are applying it to all items regardless of group or standard item/assembly, then what do you do if there is an item that exists as two separate lines with the same item (eg 100 widgets at this price and 200 widgets at that price)?
b
Every line gets a unique id. The integration adds that value for all non-group items so the script just handles lines that are blank. We don't have any situations where one group has the same item as a component more than once. That would definitely be an issue with our exact approach. The same item can be on the transaction more than once since the SF quote line id would be different and keep the custom identifier unique.
d
okay that makes sense. I think that could work for us! Thanks very much for your help ben, I owe you a drink!
👍 1