I am coming to the realization that my Netsuite assemblies are sloppy, I have lots that don't have "Department" field entered or the BOM name is the same as the item # which has been very difficult to navigate on saved searches and sometimes coming up blank. Can someone assist in the process of export all my assemblies so I can fill in or edit what needs done and re-import? We are moving to WIP and Routing and I have been fighting tooth and nail trying to get ALL assemblies I have in one spot the process the data

Do you have advanced bill os materials enabled?

yes

What do you mean by this? The BOM name is a free text field; you define the name

this is my search critera, am I using the correct one to pull BOMs?

Yes name should be the correct field unless your company has created a custom field you consider to be the name of the BOM I’m use to the revision bieing called bill of material revision.name. Not revision.name But every account is different

well and we also use a thing called Blend for some items

If the record was created manually in the UI, then most likely it won't have an external ID> usually the external ID is used when a record is created via CSV import or External Integration

saving this for after I get through WIP and Routing implementation. It's been kind of a nightmare

The routings also pose a similar issue. I would try to come up with the naming syntax for all these records in advance, so you can implement WIP with the correct naming.

this is what we the NS rep had me do

Are these routings?

yes

is 58-0567 an item number?

yes and used as the BOM name 🤮

werid

its been slapped together before I got here

Usually the work center is in the routing step, not the overall routing

I plan on getting through wip and routing and then going through it again to clean it up in Sandbox and dragging over to production side

You can do imports for all these records. In the past I usually create 1 master template for all these records and do multiple imports to create/update them. It usually takes about 4 - 5 imports to create 1 assembly

Why wouldn't you just have all the fieldID's you need as headers and just do one big one?

Because it's 4 separate record types and you can only upload 1 record type at a time First is create the Assembly Item, Then create the BOM record Then create the Revision record and assign components Then assing the BOM to the Assembly record (usually as the Master BOM) Then create the Routing record and assign the Assembly and BOM

makes sense!

One caveat to the routing record is that if you have multiple locations you need to make one per location (i think)

so I would need to export them out one record type at a time and then go through and tidy up and then re-import

You can do each import in bulk

I was worried about the mulitple locations and routing but there is only one step that won't happen at "plant 2"

(netsuite does have a 25,000 row limit to CSV imports but you can do multiple files)

I don't think anything I would do would be that big but good info

Most of the "Master Spreadsheets" i've built for this end up with like 80-90 columns when all said and done

I think I would rather split it by sheets?

If you are just doing a one time clean up effort then that works...but if you are creating a lot of assemblies frequently then it might be good to just make one master file and upload it 4 times (1 for each record type)

I've also been learning alot about excel lol. Figuring out how to multiply cells x4 onto another sheet and such

yeah that helps

I may DM you later on for a rundown on CSVs if you don't mind when I'm trying to clean this up

yes that works...reach out anytime

I've already looked at forms to figure out what I'm going to make mandatory fields because these people never fill everything out

CSV's can be a little tricky/frustrating at first, but once you get the hang of them its not too bad

I feel like CSVs and knowing fieldIDs is the only reason we pulled a NS rep in