Unanswered

Dataverse Dataflow lookup field not accepting alternate key

(1) Share

Report

Posted on by james_hathaway

427

When creating a dataflow to sync data from a SQL databse into Dataverse, the Lookupfield of the destination table are not accepting the correctly configured alternate key.

The dataflow fails with an error message:

"0x8006088a: The key in the request URI is not valid for resource 'Microsoft.Dynamics.CRM.sdx_itemparents'."

The data sent to dataverse by the dataflow is: "sdx_Item@odata.bind": "/sdx_items(sdx_productcode='XX7281.60')" and the "sdx_item" table has an alternate key set to the "sdx_productcode" field:

Dataflow column mapping: (There happens to be 2 lookup fields to the same "Item" entity, as this table is setting up a "parent" relationship form Item -> Parent Item)

So it should perform the lookup to the record correctly, but is not working.

I have also checked that the Key is active (using Classic mode):

I have searched all Microsoft Documentation and the forums, and cannot find any reference to this error anywhere.

Has anyone else seen this error?

Any ideas why this lookup is not working?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Sort by

PHalseyKMS 20 on at

Like (0)

Report
Copy link

Link copied!

I have noticed a similar error occur in one of my dataflows, but it's inconsistent, sometimes the error occurs on one table mapping and on the next run that record works but the error occurs on a different table.
Also only some records fail for a table and they all have the same key construct.

Was this reply helpful? Yes No
chico 638 on at

Like (0)

Report
Copy link

Link copied!

seeing this failure as well, but very inconsistent.
The refresh runs every 2 hours and maybe once a day, it fails with this error,,,

Was this reply helpful? Yes No
PBIQueryous 2 on at

Like (0)

Report
Copy link

Link copied!

Notice how no-one has explained this error? IT's 2023 and this is still happening.
The dataverse is an illogical, unintuitive, largely undocumented wilderness with random bugs, random failures, massive inconsistencies and restraints. It's a mess.

Answer this, why do dataflows have this same error, occur randomly, on random different rows, with no real explanation?

"message":"The key in the request URI is not valid for resource 'Microsoft.Dynamics.CRM.tbl.tablename'. Ensure that the names and number of key properties match the declared or alternate key properties for the resource '

The names and number of key properties does match the declared key properties - BECAUSE IT'S USING DATVERSE GENERATED GUIDS TO CHECK FOR UNIQUENESS. If the key properties were different, it WOULD fail for the entire column, but it doesn't - it decides, one or two records will fail out of 100s - at random.

This is a terrible experience for users, especially when it's designed for citizen-developers with no coding knowledge.

Was this reply helpful? Yes No
chico 638 on at

Like (0)

Report
Copy link

Link copied!

We see this error, Daily.
Funny, my inbox had a notification from a new post on this thread and the message directly next to it was an alert from power platform to indicate a Dataflow refresh had failed.
and yup, the same error....
this proccess runs every hour and on average it fails 1-2 times a day due to that error...

I just call it the "Fog"

Was this reply helpful? Yes No
DW-24091901-0 2 on at

Like (0)

Report
Copy link

Link copied!

Wild Ass Guess.

Could it be that the reason it is happening is because a record is being created at the same moment that your query is happening and there is something unusual in the alternate key field?

If you add a new auto-generated alternate key column to a Dataverse table with existing data, new rows will get a new autogenerated value in that column, but existing rows will be null.

XRM Toolbox has a utility called Alternate Key Manager which will populate the autogenerated value for that field. However, if the tools is creating new alternate keys at the same time as users are trying to create records, the users can experience a save/create failure due to their record trying to write a duplicate alternate key.

Not sure if this helps, but it may be a similar issue.

Was this reply helpful? Yes No