topic Upsert - I thought child record would use the mappings from 2nd object in DemandTools

Upsert - I thought child record would use the mappings from 2nd object

michael-wtds — Tue, 26 Dec 2023 18:51:51 GMT

I last used a Upsert scenario with vs. 5.32.0 that would create activities related to contacts using matching for Contacts and Tasks, where the task description and date were mapped from the file, and constants are used to set the other default task fields. Then on the Contact matching step, I have it set to create child task records.

However, when I went to run this today using version 5.33.0, it created the contact related task, but with only the task fields from the Task constants. The mapped Task fields were not included.

Am I missing something, or is this an issue with the new version?

Here's the mapping screenshot for tasks where 2 fields are mapped, and 5 constants are set.

The preview results don't include the task mapped fields from the source file, but the the constants are shown.

Re: Upsert - I thought child record would use the mappings from 2nd object

michael-wtds — Tue, 26 Dec 2023 20:19:39 GMT

Never mind, this was user error. 😞

It looks like the input file was default to the wrong source tab.

Re: Upsert - I thought child record would use the mappings from 2nd object

AnthonyValidity — Tue, 26 Dec 2023 19:21:36 GMT

Hi @michael-wtds ,

If this worked in a previous version, I recommend opening a Support ticket. Please provide to them your Audit Logs and App Logs.

Regards,