SFDX-Data-Move-Utility: [QUESTION] - Error on parent lookup

Describe the bug Error re: missing parent lookup records: “…missing parent lookup records were found. See MissingParentRecordsReport.csv file for the details.”

This error is new, and there have been no changes to the underlying data model (objects, fields) for objects spec’d in the export.json. This job has run many times successfully in the last few years. The last time we ran it (and when it was successful) was probably 3 months ago. This may be relevant, but I’m also getting this error at the beginning of the log output:

(node:45632) Warning: Deprecated config name: apiVersion. Please use org-api-version instead. (Use node --trace-warnings ... to show where the warning was created)

I found an issue (completed) here on this site for the above, but the suggested fix did not work to remove the error.

To Reproduce Execute the job: sf sfdmu run --sourceusername PROD --targetusername UPHOFF

Expected behavior I expected SFDMU to extract and load the 3 “parent” objects’ data, then perform the necessary lookups to establish the links from the fourth object back to the 3 “parent” objects. The fourth object is a kind of “junction” object between the 3 others.

export.json (will attach)

Log file (will attach)

_target.csv file. A few rows from the offending target file, ICD_to_HCC_Code_Mapping__c_insert_target.csv:

CreatedDate,Errors,HCC_Code__c,HCC_Version__c,ICD_Code__c,LastModifiedDate,Name 2024-02-16T16:54:03.000+0000,Could not locate this record in the API response.,#N/A,a7H8L0000008RBlUAM,#N/A,2024-02-16T16:54:03.000+0000,a7I6S000000F9oA 2024-02-16T16:54:03.000+0000,Could not locate this record in the API response.,#N/A,a7H8L0000008RBnUAM,#N/A,2024-02-16T16:54:03.000+0000,a7I6S000000F9pN 2024-02-16T16:54:04.000+0000,Could not locate this record in the API response.,#N/A,a7H8L0000008RBpUAM,#N/A,2024-02-16T16:54:04.000+0000,a7I6S000000F9rk 2024-02-16T16:54:04.000+0000,Could not locate this record in the API response.,#N/A,a7H8L0000008RBoUAM,#N/A,2024-02-16T16:54:04.000+0000,a7I6S000000F9sx 2024-02-16T17:14:26.000+0000,Could not locate this record in the API response.,a3a8L000000cbO8QAI,a7H8L0000008RBoUAM,#N/A,2024-02-16T17:14:26.000+0000,a7I6S000000FByC 2022-12-17T00:30:45.000+0000,Could not locate this record in the API response.,a3a8L000000cbO8QAI,a7H8L0000008RBmUAM,#N/A,2022-12-17T00:30:45.000+0000,a7I6S00000163Lf 2022-12-17T00:39:17.000+0000,Could not locate this record in the API response.,a3a8L000000cbO8QAI,a7H8L0000008RBlUAM,#N/A,2022-12-17T00:39:17.000+0000,a7I6S0000016UJX 2022-12-22T16:51:44.000+0000,Could not locate this record in the API response.,a3a8L000000cbO8QAI,a7H8L0000008RBkUAM,#N/A,2022-12-22T16:51:44.000+0000,a7I6S0000016wxX

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (6 by maintainers)

Most upvoted comments

Hello, @buphoff-villagemd

Thank you for reporting a bug. I will take a look at it as soon as possible and let you know of any updates.

Cheers