[sklett]

I’ve gone through the help a couple times now and I’m either missing the section that covers what format the Import Assistant wants OR… it’s not discussed.

I have a simple test file with one Assembly item and 5 members. I’ve been using trial and error for 3+ hours now. I’ve tried repeating the rows for each member, I’ve tried blank rows except member and quantity, I’ve tried one file, two files…

So if anyone has imported Assembly records in a single file, can you tell me what the magic format is? I’m performing an Add operation if that makes a difference.

I’d post my CSV code here but because if the lamo formatting it won’t look correct and will just be more confusing I think.

Thanks for any help.
This is a cached copy. Click here to see the original post.

[JMUnderwood]

RE: Assembly import – tired of trial and error

Originally posted by sklett

. . . So if anyone has imported Assembly records in a single file, can you tell me what the magic format is? I’m performing an Add operation if that makes a difference..

Steve,

I think that’s the problem: You need TWO files to import/ADD Assembly Items:MAIN Assembly Item FileImport all the data about the AI other than the Members/BOM
One row per AI
I recommend you assign External ID to every AIUse the Ext ID to link to Member Items file and for all future Import/Updates

Members/BOM fileA very simple file that contains just a few fields/columnsRef link to AI in File #1 — Use AI Ext ID
Member Item — Use either Ext ID or Int ID
Quantity
One row per Member Item

The real key is using Ext ID to reference ALL Items.

We assign a unique Item Code (some would call it SKU) to every Item and assign it to the Item Display Name. The Item “Item Name” is a unique short descriptive name for the item. We assign the same value to both the Display Name and the External ID.

If this doesn’t clear it up for you, shoot me an email (or call) and I’ll try to help get you going.

[sklett]

RE: Assembly import – tired of trial and error

Hi Jim,

Thanks a lot for the detailed response, I appreciate it. I read your post and banged out two test files real quick and as soon as I clicked the “Multiple Files” option I had my “ah-ha!” moment. See, I was trying to use a single file (which I had read on the UG and been told by support WAS possible) and was frustrated my the elusive magical format of the AI and Member data. But now with the two file option and your notes I totally get it.

I used my ItemName as my external Id and that works well for us. What I’m basically doing is converting Kits to Assemblies so I’ve setup a nice saved search that spits out my kit data then I massage a bit and import back as Assemblies.

Anyway, thanks again for the great reply.

[StephQ]

RE: Assembly import – tired of trial and error

Originally posted by sklett

Hi Jim,

Thanks a lot for the detailed response, I appreciate it. I read your post and banged out two test files real quick and as soon as I clicked the “Multiple Files” option I had my “ah-ha!” moment. See, I was trying to use a single file (which I had read on the UG and been told by support WAS possible) and was frustrated my the elusive magical format of the AI and Member data. But now with the two file option and your notes I totally get it.

I used my ItemName as my external Id and that works well for us. What I’m basically doing is converting Kits to Assemblies so I’ve setup a nice saved search that spits out my kit data then I massage a bit and import back as Assemblies.

Anyway, thanks again for the great reply.

There definitely needs to be more documentation regarding the import format for Assembly Items or sample templates to download.

[StephQ]

RE: Assembly import – tired of trial and error

Originally posted by JMUnderwood

Steve,

I think that’s the problem: You need TWO files to import/ADD Assembly Items:MAIN Assembly Item FileImport all the data about the AI other than the Members/BOM
One row per AI
I recommend you assign External ID to every AIUse the Ext ID to link to Member Items file and for all future Import/Updates

Members/BOM fileA very simple file that contains just a few fields/columnsRef link to AI in File #1 — Use AI Ext ID
Member Item — Use either Ext ID or Int ID
Quantity
One row per Member Item

The real key is using Ext ID to reference ALL Items.

We assign a unique Item Code (some would call it SKU) to every Item and assign it to the Item Display Name. The Item “Item Name” is a unique short descriptive name for the item. We assign the same value to both the Display Name and the External ID.

If this doesn’t clear it up for you, shoot me an email (or call) and I’ll try to help get you going.

I tried to import new member items in with the main Assembly item (using Linked file) and got an error saying “Invalid item reference key Battery Part 1”).

Do I have to create the member items in the system first or can I import them for the first time with the parent Assembly Items??

[JMUnderwood]

RE: Assembly import – tired of trial and error

Originally posted by StephQ

I tried to import new member items in with the main Assembly item (using Linked file) and got an error saying “Invalid item reference key Battery Part 1”).

Do I have to create the member items in the system first or can I import them for the first time with the parent Assembly Items??

You have to import from the BOTTOM up.

So yes, you must first create (by import or UI) all Member Items before you import the Assembly Item. We have found the best practice is to import the member items first, assigning their External ID to be the same as the Item Display Name/Number.
We use the Item Display Name/Number to store our SKU (which is a 5 Digit number).
We enter a descriptive name into the Item Name field.
Then when you import the Assembly Item, use the Member Item External ID on the Excel file to map to the NetSuite Member Item field. You will need to click the pencil icon on the mapping line for the Member Item and set Reference Type to “External ID”.
This tells NetSutuite to use the External ID of the Member Item to identify the Member Item
Hope this helps.

[Suite_E]

RE: Assembly import – tired of trial and error

Originally posted by JMUnderwood

View Post

You have to import from the BOTTOM up.

So yes, you must first create (by import or UI) all Member Items before you import the Assembly Item. [LIST][*]We have found the best practice is to import the member items first, assigning their External ID to be the same as the Item Display Name/Number.

Thanks JM! You really got me through a stuck spot!

– Miguel

[Suite_E]

RE: Assembly import – tired of trial and error

Originally posted by sklett

View Post

I’ve gone through the help a couple times now and I’m either missing the section that covers what format the Import Assistant wants OR… it’s not discussed.

I have a simple test file with one Assembly item and 5 members. I’ve been using trial and error for 3+ hours now. I’ve tried repeating the rows for each member, I’ve tried blank rows except member and quantity, I’ve tried one file, two files…

So if anyone has imported Assembly records in a single file, can you tell me what the magic format is? I’m performing an Add operation if that makes a difference.

I’d post my CSV code here but because if the lamo formatting it won’t look correct and will just be more confusing I think.

Thanks for any help.

Here’s how I imported the BOM as one file:Set up CSV file with assy part# and description in first few columns (repeated in each row), and member part#, member description, qty, and [member part#][single space][display name] in last few columns. NOTE, the [member part#][single space][display name] is needed because our company has the “Show Display Name with Item Codes” general preference enabled; you can skip this column if you don’t have the preference set.
Import the file as inventory items, with data handling set to add new items only, and set up the import map so the member part# is also mapped to the External ID field (this is because NetSuite wants either the External or Internal ID for the assembly members; it will reject item names). Ignore the extra fields like assy part# and [member part#][single space][display name] fields. This import will add any missing member items. Be careful you don’t duplicate parts if you use subitems.
Import the exact same file again, but this time as an assembly item, with data handling set to add or update items (this is so NetSuite will create the assembly item with one member for the first line of your CSV file, then keep adding to the list of member items with each row in your CSV file). If you have the “Show Display Name with Item Codes” general preference enabled, then set up the import map so the [member part#][single space][display name] field in your file is mapped to NetSuite’s Members 1:Item field, otherwise map this NetSuite field to the External or Internal ID of your member part# field.

Happy importing!

– Miguel

[Author]

Posts