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 Change object.
Prerequisites: You must create Lifecycles (workflows) and Categories for all types of Changes you intend to load. Example Change categories: ECO, Deviation, ECR, Stop Ship. You must also give yourself the permission set Propel Override Business Rules.
How to Migrate Approvals from a Legacy PLM System: If you are migrating data from another PLM system, that system likely has approvals for its ECOs and other Change objects. It is easiest to consolidate each Change's approvals into a big, custom text field. Salesforce does not have an easy way of creating "real" back-dated approvals for legacy data.
Create these columns in your import file:
1. Change Number
5. Status (you actually load this later, do not map when initially loading Changes)
6. Primary Key (should be equal to Change Number)
7. Approved (TRUE or FALSE)
8. Approved Date (Example: 2017-08-03) Excel format: yyyy-mm-dd
9. Approved Date Time (Example: 2017-08-03T00:00:00Z) Excel format: yyyy-mm-dd"T00:00:00Z"
Most customers have several other Change custom fields also. Create the appropriate columns in your import file.
Load the Changes using either the Data Loader or the Import Wizard.
Loading Change Statuses
You must perform an extra step to load Change statuses.
1. Create a new report in Salesforce.
Report Type: Change Phases with Change
Change: Change Number
Change Phase: Change Phase Name
Change Phase: ID
2. Run the report.
3. Export the results to Excel.
This report will have all the possible Change Phases, along with their IDs, for every Change you have loaded. For example:
4. Merge these Change Phase IDs into your original Change import file. In your import file match the Change Number and its human-readable status to the corresponding Change Phase ID found in the report. For example:
5. Use the Import Wizard or Data Loader to do an UPDATE to the Change object. Match on Primary Key. Import ONLY the column Change Phase ID.
6. When you have completed the import use Propel to spot-check a few Changes. Confirm that the correct Change Phase is shown. For example:
Now that you've successfully loaded Changes you need to load each Change's Affected Items. This process is described in our article Dataload: Affected Items (Changes).