Help Center

Dataload: Items and Item Revisions

Intended Audience: Propel Consultants and Partners and experienced Salesforce Administrators who are comfortable working with large data sets and importing directly into Salesforce custom objects.

Note to Users: If you need to import data from a spreadsheet or CAD system please see the article Import Item Data. The Propel import tool is designed for Propel users and provides an easy way to import data for most use-cases.

Scope: This document describes how to load data into Propel for large sets of data, and particularly for dataloads containing multiple revisions of Items, BOMs and AML, where each revision must be released. Typical data sets include data from legacy PLM and ERP systems.

Tools: This article discusses loading data using standard Salesforce import tools: the Import Wizard and Data Loader. Prior knowledge of these tools is assumed. See our article on Bulk Updates for details about how to use the Data Loader.

Required Privileges: You must have Salesforce System Administrator privileges to use the tools referenced in this article.

Disclaimer: Propel Support is not responsible for data integrity errors or data loss resulting from importing data directly into Salesforce custom objects. It is assumed that the reader of this article is experienced with Salesforce objects and schema and has prior experience performing data migrations.

Technical Support: The Propel Support organization cannot assist with data migration efforts. You may choose to contract with Propel Implementation Services for paid assistance with these activities.

Environment: It it strongly recommended that you perform dataload activities in a Sandbox environment first.

 

Order of Dataload Activities

You will typically load data into the following Propel objects, in this order:

Item
Item Revision
Assembly
Manufacturer (Account)
Manufacturer Part
Manufacturer Item
Change
Affected Item

This article covers the Item and Item Revision objects.

 

ITEM Object

Load three fields to construct a record:

  1. Import Category Name
  2. Item Number
  3. Primary Key (make it the same as Item Number)

Sample Import File (also see attachment to this article):

 

Data Loader Mapping Instructions

Use auto-mapping; all fields are named exactly as needed. Here is the mapping:

 

Import Wizard Mapping Instructions

Choose this option:

 

(Set all other options to None)

The wizard will automatically map fields correctly:

 

ITEM REVISION Object

Load three mandatory fields to construct a record:

  1. Import Master Item Name (populate with item number)
  2. Description
  3. Primary Key (see notes below)

In addition, load these fields:

  1. Revision
  2. Lifecycle Phase
  3. Released (TRUE/FALSE)
  4. Release Date (Example: 2017-08-03) Excel format: yyyy-mm-dd
  5. Release Date Time (Example: 2017-08-03T00:00:00Z) Excel format: yyyy-mm-dd"T00:00:00Z"

Sample Import File (also see attachments to this article):

 

Item Revision Primary Key Notes

If you are migrating data from another PLM system that uses Change Orders, construct the Primary Key with item number, revision and Change Order:

100-00023:A:ECO-00456

If the item to be migrated is unreleased and doesn’t have a Change Order, leave the last part of the key blank:

100-00765:A:

If you are migrating data that doesn’t include any Change Orders, construct the Primary Key like this:

200-09970:A:NoChangeOrder

The primary keys are used only for the purpose of matching data during dataloads, so you have some flexibility in how you choose to construct them. For data migrations from other PLM systems you may need to use that system’s revision ID to guarantee uniqueness. For example, Arena allows the same item number to have multiple revision values that are the same, e.g. three Revision B’s for 100-00765. In this case you want to use the Arena GUID as the primary key.

 

Data Loader Mapping Instructions

Use auto-mapping; all fields are named exactly as needed:

Note that the Data Loader doesn’t do field lookups automatically. If some of the Item Revision custom fields are lookup fields to another object, you’ll need to provide the Salesforce IDs of those lookup values. This is extra work, so you might want to load Item Revisions with the Import Wizard instead.

 

Import Wizard Mapping Instructions

Choose this value: 

The wizard will automatically map fields correctly EXCEPT for the first one. The default mapping will not work:

Instead, map the values like this:

Complete the import.

 

 

 

 

 

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.