Announcements
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?
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/UCnGNN3hdlKBOr6PXotskNLAFollow me on Twitter : @rampprakashdBlog : https://microsoftcrmtechie.blogspot.com
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.
As there is not a 1:1 you have to mimic it ether
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 421
WarrenBelz 345 Most Valuable Professional
Kalathiya 278 Super User 2026 Season 1
