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:
This article covers the Affected Item object. Note that importing Change Affected Items and Quality Affected Items is slightly different. Quality Affected Items are covered in a separate article.
Prerequisites: Your user account must have the permission set Propel Override Business Rules.
AFFECTED ITEM Object
Create these columns in your import file:
1. Item Revision Key (Primary Key of Item Revision record)
2. Change Key (Primary Key of Change record)
Optional, but recommended:
3. Primary Key. You’ll have to make this up. It can be a unique sequential number, or you can construct it like this: Change Number + Item Revision Primary Key. Why is this recommended? Because if you have any failures in your import and you want to re-import with the ADD&UPDATE (Upsert) option you’ll need to match on Primary Key.
In addition, load values for disposition fields and custom fields as needed. For example:
(Other custom fields as needed)
Import Wizard Mapping
Choose these options:
Map as follows:
Complete the import.