Sample Template: Creating New Inbound Shipment records with CloudExtend

XLNS | Learn how to work with Inbound Shipment Records and Purchase Order Line Unique Keys

Updated over a week ago

While Updating/Creating new Inbound Shipment records using CloudExtend Excel, there is one Gotcha that users need to be aware of. The Shipment Item field looks like it contains a NetSuite item but if you look carefully it is actually a reference to a field on the Purchase Order that contains the item.

In the inbound shipment template screenshot shown below, on item 1017, you can notice that internalID is populated as [[27522]] when you download an existing record.

The issue here is it is not the internalID of the item in context, rather it is a reference to the Line Unique Key of the item in the linked Purchase Order PO#21. 

How to find Line Unique Key

Users can find the Line Unique Key by creating a saved search on PO as below. Alternatively, if you're manually creating an inbound shipment record enter the Purchase Order number in Excel and then use the picklist in the Shipment Item field. You'll see a list of items relevant only to that PO and when you select the item the correct internalID will be added.

Tying it all together with CloudExtend

As part of your workflow, you'll want to first use the CloudExtend raw data download (if you're not manually adding PO's in Excel) to quickly retrieve your PO's and look up the Line Unique Key using Excel VLOOKUP from the related PO and place the value in the Items List: Shipment Item field in the proper format  of [[lineunique key]].  

Did this answer your question?