Unanswered

ID as Primary Key in Dataverse Table

(1) Share

Report

Posted on by JK-25091409-0

Is it possible to create a unique primary key field "ID" with autoincrement that acts like other relational databases? It seems to work sometimes, but I don't understand completely but if I add to a form I want it to populate and increment automatically and I want to be able to reference in other tables, as a many to many relationship, like one field having values from the IDs of my table "1,2,5,7".

Categories:

Power Apps Pro Dev & ISV

I have the same question (1)

All responses (4)

Answers (1)

ronaldwalcott 3,847 Super User 2025 Season 2 on at

Like (2)

Report

Could be done but why would you want to?

Dataverse table already include a unique key value even if you don't use it. You can create your own primary key which you can use in relationships and it does not have to be an autoincrement number.

You can set up a many to many relationship as described below

Create many-to-many table relationships in Microsoft Dataverse overview - Power Apps | Microsoft Learn

Was this reply helpful? Yes No
JK-25091409-0 98 on at

Like (0)

Report

@ronaldwalcott

I tried many to many relationships but I didn't like it because there was no way to see the relationship data in the tables. So I started putting comma separated multiple "ID"s in a column (1,2,5,7, etc).

Was this reply helpful? Yes No
Suggested answer

stampcoin 5,058 Super User 2025 Season 2 on at

Like (2)

Report

JK-25091409-0 Hi,

You can try to add one , Data type= # Autonumber, and define it as Business required, you can define Prefix if you'd like.

then you can refer it as you own id.

Was this reply helpful? Yes No
Verified answer

ronaldwalcott 3,847 Super User 2025 Season 2 on at

Like (2)

Report

If you need to understand the relationships from the joining table creating a more informative unique primary key in the two tables would probably be more descriptive than using integers.

Something like this which you can create and manage.

Each row still has a unique key (GUID) provided by Dataverse and the primary key that you use can be anything you want and does not have to be a sequential integer so you would not have the concern of two users getting the same number for a record because Dataverse does not provide the facility to assign keys in this manner.

If this answered your question please mark it as such

If this answered your question please mark it as such

Was this reply helpful? Yes No