Unanswered

One-to-one table relationships

(0) Share

Report

Posted on by anglosaxon

I am new to Dataverse. I discovered yesterday there there is no natural way to create a 1:1 relation between tables.

I've read a couple of articles on work-arounds but they add additional complexity when I was hoping for less complexity in a lo-code framework.

How do people here resolve this?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Ram Prakash Duraisamy 5,593 Super User 2025 Season 2 on at

Like (0)

Report

Hello @anglosaxon

As per OOB Behaviour, we are only having

1:N

N:1

N:N

Relationships alone, Can you please share your requirement to help the same

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Follow me on Twitter : @rampprakashd
Blog : https://microsoftcrmtechie.blogspot.com

Was this reply helpful? Yes No
TRamZ 13 on at

Like (0)

Report

I would also like to use 1:1 (one-to-one) relationships. I have related data that technically could all reside in one table but I would prefer to segment it out into a separate table for governance and separation of concerns. Table B is related to Table A and there will only be one related record in Table B to Table A. When I include Table B data as a sub-entity on Table A's form, I want to see a form for the related Table B record, not a subgrid. I have users that I want to have read-only access to Table A but write access to Table B. The 1:N technically works but is not the best user experience when the N is actually always 1.

Was this reply helpful? Yes No
Fubar 8,338 Super User 2025 Season 2 on at

Like (0)

Report
As there is not a 1:1 you have to mimic it ether
Create the extra data as a Parent record to the main record, or
Create it as a Child record, and when you create the Child record add it to a Lookup on the main record (this approach works where there may be different 'versions' of the extra info so you link the latest version to the Lookup and older versions are still available as child records)

Was this reply helpful? Yes No