Warning about missing parent lookup records seems odd.


Question.

Why does the Plugin generate a warning about missing parent lookup records for {OBJECT_NAME} like: {OBJECT_NAME} N missing parent lookup records were found. See MissingParentRecordsReport.csv file for the details. when finally all lookup fields are being populated for this object in the Target, making the warning seem odd?


Answer.

The warning about missing parent lookup records may appear even if all lookup fields are being properly populated in the Target.

This can happen if the Plugin tries to insert a child record while it expects a parent record to exist but doesn't find one (e.g., when the parent record isn't inserted in the Target org yet). In this case, it generates the warning as a precaution, but it continues with the operation and properly populates the child lookup fields.

However, if you're sure that all lookup fields are being correctly populated, you can safely ignore this warning.

You can prevent the Plugin from prompting the user to stop execution when this warning appears by setting the promptOnMissingParentObjects configuration option to false.

Additionally, you can suppress stdout all warnings by adding the --nowarnings flag to the command line.


See also:

Basic examples

Last updated on 15th Mar 2024