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.
Change vs. Quality: This article covers the Affected Item object. Note that importing Quality Affected Items and Change Affected Items is slightly different. Change Affected Items are covered in a separate article.
Prerequisites: Your user account must have the permission set Propel Override Business Rules.
AFFECTED ITEM Object (Quality)
Create these columns in your import file:
1. Item Revision Key (Primary Key of Item Revision record)
2. Quality Issue (Quality record number, such as CAPA-00023, to be replaced later with Quality ID)
In addition, create columns for custom Affected Items fields as needed. For example:
Do not use the Import Wizard for loading Quality Affected Items. Why? The Import Wizard will fail if you have an item associated with two different Quality records. It will give you an error relating to duplicate IDs. You need to use the Data Loader for Quality Affected Items. Not only do you need to use the Data Loader, you need to use a batch size of 1. (Instructions for changing batch size included later.)
Finding and Merging Quality Object IDs
1. Before you can load Quality Affected Items you need to run a Salesforce report to find the Quality object IDs:
Report Type: Quality
Include these fields:
Quality: Quality Number
2. Run the report and export the results.
3. Use a VLOOKUP or other method to merge the Quality IDs into the import file (see example below).
4. Rename the columns in your import file to match what the Data Loader expects. In particular:
The Quality ID field should be called: Quality Issue
The Revision Primary Key field should be called: Item Revision Key
The Affected Items Primary Key field should be called: Primary Key
Sample import file:
Run the Data Loader:
1. First, change the batch size to 1. This is so the Data Loader doesn’t complain about items with multiple Quality associations in the same batch. To do this:
a) On the main screen of the Data Loader, go to Settings.
b) Choose a Batch Size of 1.
c) Save your changes. (If you are using a PC with a small screen, you won’t see the Save button. Simply hit Enter and your changes will be saved. Look at Settings again to confirm.)
A batch size of 1 makes the import run very slowly. After the import don’t forget to change the batch size back to 200.
2. Type of import: Upsert
Select Salesforce object: Affected Item (PDLM_Affected_Item__c)
(Choose file, click Next)
3. Select the field for matching on PDLM_Affected_Item__c: PDLM_Primary_Key__c
4. Choose your related objects: (don’t choose anything; click Next)
5. The required part of the mapping is this:
Item Revision Key --> PDLM_Item_Revision_Key__c
Primary Key --> PDLM_Primary_Key__c
Quality Issue --> PDLM_Quality_Issue_lk__c
6. Complete the import.
7. When you're finished importing Affected Items don't forget to change the Data Loader batch size back to 200.