It appears that CDS will only let you choose exactly one field as a key for any one custom entity, which is ok to start.
Then it also necessary that the key field is a required filed of the entity, this is logical.
However, I was able to set a field which is not unique as the key field, which is not logical.
Is this a bug?
Also, when I changed the key field, the foreign key of another custom entity that was looking up to this table did not change.
In other words the lookup filed still had the old text values of the old key and the lookup was broken, no warnings no nothing.
Is this intentional behaviour?
Many thanks and keep up the good work.
Solved! Go to Solution.
When trying to create a compund key a timeout error is displayed:
If you refresh and go back the changes have not been saved. If you click the save button a second time a different error message displays:
Despite the encouragement to create a compund key with "Key Fields (?)", the message says this is not supported.
Please can you confirm whether or not compound keys are meant to be supported?
I reproduced this issue, and I would collect and report this issue, thanks for your feedback.
I test with issue with two key fields and I get the message which says that “A valid primary key must contain only one field for custom entities”. With only one key field, it can be saved successfully. It seems that compound keys are not supported yet. I would try to confirm if there is an official document clarifying this issue.
Learn how to create your own user groups today!
Explore the latest tools,training sessions,technical expertise, networking and more.
Check out the new Power Platform Community Connections gallery!
Congratulations, the new Super User Season 2 for 2021 has started!
Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.