cancel
Showing results for 
Search instead for 
Did you mean: 

How to add child records when provided file does not have parent object SFDC ID

LizK
Enthusiast

I have parent object (application) and child object (advanced credit course). On parent application object the NAME field, which is auto number, is the application number. On the child object, the corresponding field with application number is master-detail field. The file I have for insert is list of advanced credit courses and  includes column where the parent application number is provided. I used auto map for the insert of child records for the various parent applications. But the records failed to insert. Didn't like the application number, master-child data type field. I'm guessing that somehow I now have to ferret out the parent record's actual SFDC ID and jam that onto the spreadsheet as well before trying again. That seems odd to me if true. This is parent-child relationship that I would think DT should see and leverage during insert.  I'm a DT user prior to V5 so a bit confused as to how get things done in the newer DT interface.  Any advice greatly appreciated.

2 REPLIES 2

Pugs_Validity
Validity Team Member
Validity Team Member

Hey @LizK - For this instance, we'll want to perform an Upsert operation in the Import module utilizing the Match Conditions method. Upsert with Match Conditions allows us to pull-in multiple objects for consideration. In your case, we'll be matching to the Application object so that we can ultimately, insert the Advanced Credit Course under them. In my screenshots below, I'm showing Account, as the parent object and Contact as the child object. While not necessarily in your specific instance, the order we compare against the objects in an Import module operation is importaint, as Import will stop once it finds a match and not continue on looking for matches against the other objects in consideration. I mention this, because if you compare against Advanced Credit Course (ACC) THEN Application, you may not see new ACCs created since the scenario may find a matching ACC that already exists in that given setup. I'm going to assume we aren't concerned about matching to existing ACCs in your situation and that all parent Applications already exist, so we will match against Application (Account) and then ACC (Contact). You'll want to map all applicable information for the ACC from your spreadsheet and then most importaintly for the Application object, you'll need to map the master-detail field from your spreadsheet to the Name field on the Application, set it to do Do Not Update to be safe for case sensitvity. 

Pugs_Validity_0-1753815786943.pngOn our match steps, we'll be matching on Name and asking DemandTools to Create child object: ACC. As long as your spreadsheet has all the approrpriate parent application number's, we shouldn't have to be concerned with other fields & objects on the mach steps. You may want to use the Unique Field comparison type (new in DTV Version 5.45) to account for any potential case sensitivity issues between SF and spreadsheet. 

Pugs_Validity_1-1753816753452.png

That should do it! Since I can't see your exact scenario setup, I apologize if you are doing any of this already. If you are doing the same steps yet still experiencing them not inserting correctly, please reach out to us at DemandToolsCOE@validity.com so we can investigate it further!

LizK
Enthusiast

7/30/25 - Thanks for detailed explanation and screen shots. Unfortunately, still unable to get the new records created. Will email into address provided and then maybe someone can contact me to figure where I may be going wrong. Tks! LizK