Hi @CWesener, Thanks for the response. This reminds me with the property "Unique" in Access Web Apps database.
2 things I would like to mention: -
1. Creating a key via the PowerApps studio (online) will not prevent duplicating a record. This occurred in my tenant at least and I am willing to organize an online session so your team checks by themselves.
I trued the Solution explorer, checked my index which I created from PowerApps studio to find that there is one more step to be done on the key, to activate/resume. it failed anyhow because of existing duplicates I think.
I deleted, recreated, activated and it has worked perfectly then.
There is therefore somethng missing in creating a key from the PowerApps studio that need to be fixed.
2. Not all fields can be set as a Key for instance a Look up field. Now think of this scenario, I have 2 custom entities on the top of my database model, one is COUNTRY and the other is CITY. While I have entered all countries we work with, like 80 or so, cities are to be added by the users. I could create a key in CITY that is the City Name but for this is not correct in real life, as for instance, I have 2 cities called Tripoli, one is in Libya and the other is in Lebanon. So the right thing is to create a key from the concatenation of City Name and Country in the CITY entity, something not available because also calculated fields are not possible available to key feature.
The same goes for a CUSTOMER and PROJECT REFERENCE, so none of my customers would have 2 different projects under the same PROJECT REFERENCE.
what would be your thoughts handling this?
