dataflow errors with alternate key on lookup fields

[MJDBrooks]

I am having persistent problems importing data from a spreadsheet into a custom entity "ProjectlinkAccount" which has two lookup fields - one to Accounts and one to a custom entity Projects. I have an alternate key set up on each parent entity.

I keep getting an error message: {"error":{"code":"0x0","message":"Bad Request - Error in query syntax."}}

The query from one of the import rows looks like this:

https://nameremoved.dynamics.com/api/data/v9.1/brooks_projectlinkaccounts{\r\n  "brooks_accountname": "JohnBrook",\r\n  "brooks_legacyaccountid": "16",\r\n  "brooks_legacyid": "26",\r\n  "brooks_legacyprojectid": "19",\r\n  "brooks_name": "Main Account",\r\n  "brooks_projectname": "Great North Road",\r\n  "brooks_role": "Main Account",\r\n  "brooks_accountlu@odata.bind": "/accounts(brooks_brooksaccountid=16)",\r\n  "brooks_projectlu@odata.bind": "/brooks_projects(brooks_legacy_project_id=19)"\r\n}

Should the alternate key references in brackets be converted to GUIDs in the dataflow run?

[Anonymous]

Same issue here. In my case one of the two lookup attribute values has been resolved to a concrete record GUID, while the other one remains in the OData query-by-alternate-key syntax. I can see this in the synchronization log CSV file which lists the errors occured. Did file a support ticket, but support seems not competent to help any further. 

[ostola]

Hello everyone,

Do you resolved the issue??

I have the same behavior...

[bigwookie3000]

Has anyone found a solution to this yet? 

In my error, the following shows:

"name@odata.bind": "name(cr4_alternate_key=Ryan"