Importing Records utilizing an External ID located on a Parent Object

[Pugs_Validity]

The instructions below detail how you can utilize the Import module to insert child objects soley using a external ID located on a parent object. 

• For this process, we’ll be utilizing the Import module and perform an
  Upsert operation.
• This process will work with either an Org-to-Org operation or utilizing an
  import file.
• In this example, we’ll be inserting Opportunities onto Accounts using an
  External ID field on the Account object.

Step 1: We will select the Import Module and upload our file as our source.
We’ll be doing an Upsert operation utilizing the Match Conditions method.
First, we’ll select our desired child object (Opportunity), followed by the
parent object (Account) containing the External ID field.

Step 2: Next, we’ll map the fields we want to bring in from our source. For the
child object (Opportunity), we’ll map all fields from our file that we’ll want to
have on the newly created record. For the parent object (Account) holding the
External ID, that ID is the only field we’ll need to map.

Step 3: Move onto the Record Selection Criteria step. On the next page, we’ll
want to condition the child object to ID (Opportunity ID) = empty/blank. This
will ensure our file doesn’t match a child object already in our system. On the
right side of the page, we’ll select all fields on the objects we would like to
preview before executing the job.

Step 4: Next, we’ll need to start matching records. When matching the child
object (Opportunity), we can select any single field we would like. This is a
false match step, since we already conditioned to only consider child object
records (Opportunities) that have no Salesforce ID during the Record
Selection Criteria process.

Step 5: When matching to the parent object (Account), we’ll want to match
solely to the External ID and instruct DemandTools to create the child object
(Opportunity) upon matching to the parent object (Account) with the
corresponding External ID.

Step 6: For our Final Matching Conditions, we’ll want to instruct DemandTools
to Do Nothing.

Step 7: We’ll preview and confirm our results prior to executing the
Import.