You’re offline. This is a read only version of the page.
97
Hi, I was wondering if others would be willing to share their product import strategies through data migration or templates. This is for ongoing new product setup, not an initial migration. My issue is that product setup seems to span so many entities and the templates don't seem to address all of them and it's tedious to maintain a bunch of different spreadsheets for each entity. The approach I'd like to take it to create one master spreadsheet with the applicable columns from each entity in the row. Then I can build an import task that has a step for each entity and do the mapping to the correct fields for each. However, I don't think I can map the same file and sheet to multiple entities without having them upload it once per entity. An additional complexity we have is that we use auto generated ids for products which requires some sort of lookup between Products and Released Products.
Below are the entities that I can generally all condense into one sheet for 1 row per item.
In some cases, we need just these entities
Products V2
Released Products V2
Product default Order Settings v2
External item descriptions for vendors V2
Product category assignments
In other cases, we need all of these
Products V2
Released Products V2
Product default Order Settings v2
Route Versions V2
Bill of Materials Headers and Versions V2
Route operation properties V2
Product category assignments
Hi lfulk,
In data management, you need to upload the Excel sheet per entity. You can use Power Automate to read the Excel file and process data where in between the auto generated number will be used in a variable. I have done this before and intend to create a new example with a blog post soon.
If Power Automate is not the service you want to use, there is an ISV from my vendor called Connectivity Studio which would also be able to read a single Excel table and import it into multiple tables.
Share
Report
All responses (
Answers (
