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 Assembly object.
Prerequisite: First load all the Item and Item Revision records with their made-up primary keys.
To construct an Assembly record, you need to import only three fields. Propel does the appropriate lookups during the import process and correctly constructs the assembly record.
1. Import Item Revision Key
For reference, the API name is PDLM__Item_Revision_Key__c
This field should contain the primary key of the BOM parent Item Revision object, not the BOM parent Item object.
2. Import Item Name
For reference, the API name is PDLM__Item_Name__c
This field should contain primary key of BOM child Item object, not the child Item Revision object.
Note that Quantity is a numeric field with up to 6 decimal places.
4. Optional: Primary Key
Construct the key like this: Item Revision Primary Key + Item Number + Secondary Key. This field is optional but highly recommended so you can update or make corrections to data later.
5. Optional: Secondary Key
Make something up, like a random string or sequential number. You’ll need a secondary key if you need to load duplicate components on the same BOM. Why? So you can build a unique Primary Key, above. The Secondary Key is a maximum of 20 chars.
As appropriate, load these optional fields:
6. Find Number
7. Reference Designators
8. BOM Notes
Data Loader Mapping
Import Wizard Mapping
Leave all options blank (None), even those not shown in screenshot below:
Complete the import.