[BUG] - When using <sObject>.Id as externalId lookup the first match will be skipped

[krasseboehmer]

Describe the bug
When using any .Id as lookup for csv files the first match will be skipped. Any record after the first one will be mapped correctly. For the first one an entry within MissingParentRecordsReport.csv will be created, even when the correct related record is queried correctly.

To Reproduce
try to insert any record with an lookup of .Id for example:
AssetWarranty

Asset.PKey__c,StartDate,EndDate,WarrantyTerm.Id
a0b1r00000JPwF3AAL,2017-12-01,2019-12-01,4V39Z00000009XxSAI
a0b1r00000JPwFDAA1,2017-12-01,2019-12-01,4V39Z00000009XxSAI

Expected behavior
The first row gets mapped correctly

export.json

{
    "allOrNone": true,
    "excludeIdsFromCSVFiles": true,
    "objects": [
		{
            "query": "SELECT Id  FROM WarrantyTerm",
            "operation": "Readonly",
            "externalId": "Id",
            "queryAllTarget": true, 
            "master": false
        },{
            "query": "SELECT PKey__c FROM Asset",
			"operation": "Readonly",
            "externalId": "PKey__c",
            "master": false,
        },{
            "query": "SELECT AssetId,StartDate,EndDate,WarrantyTermId FROM AssetWarranty",
            "operation": "Insert",
            "master": true,
            "useValuesMapping": true
        }
    ]
}

_target.csv file.
None, because missing parent record

[hknokh]

Hello, @krasseboehmer

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

[github-actions]

This case has been marked as 'to-be-closed', since it has no activity for the 3 days.
It will be automatically closed in another 3 days of inactivity.

[github-actions]

This case has been closed, since it has no activity for the last 6 days. Feel free to reopen it, if you need more help.

[krasseboehmer]

Bug still persistent. This one was closed automatically

[hknokh]

Hello,

Thank you for reaching out.
And sorry for the very late response after the issue was accidentally closed by the bot.

According to our Support Policy, only runtime errors—critical failures that occur during code execution and stop the program with messages such as “Uncaught TypeError” or “ReferenceError”—will be handled.

Currently, we do not handle help inquiries, incorrect functionality, or other non-crashing behavior. Please consult our Help Center or developer forums.

Please review our Support Policy at: https://help.sfdmu.com/full-documentation/additional-information/support_policy

Thank you for your understanding and cooperation.

Regards.