Hi All,
We are looking to use Dataverse Web API to upsert external data into Dataverse and through our research we found that if the external key field is string type, the upsert fails. Has anyone in the community encountered the same issue?
* PATCH {DataverseWebAPI}/api/data/v9.2/new_table1(new_external_id_string=ABC12345)
-> This will throw an exception.
* PATCH {DataverseWebAPI}/api/data/v9.2/new_table1(new_external_id_integer=12345)
-> This will succesfully upsert the record.
There is no mention in the documentation that external key with string type will fail (https://docs.microsoft.com/en-us/power-apps/developer/data-platform/webapi/update-delete-entities-us...)
We ended up creating an integer external key field in a Dataverse table and also changing the external key format on external data to be integer type. This is very cumbersome as we are looking to integrate our old system to Power Platform and we have at least 10 external data sources we plan to integrate to Dataverse.
Solved! Go to Solution.
Hi @bs-dev001
Did you tried passing with single quotes?
{DataverseWebAPI}/api/data/v9.2/new_table1(new_external_id_string='ABC12345')
Please mark as Answer if it is helpful and provide Kudos
Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Hi @bs-dev001
Did you tried passing with single quotes?
{DataverseWebAPI}/api/data/v9.2/new_table1(new_external_id_string='ABC12345')
Please mark as Answer if it is helpful and provide Kudos
Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
@rampprakash thank you for your reply and adding single quotes worked like a charm. Just out of my curiosity, is this mentioned in documentations?
User | Count |
---|---|
20 | |
11 | |
9 | |
5 | |
5 |
User | Count |
---|---|
34 | |
32 | |
19 | |
18 | |
7 |