You’re offline. This is a read only version of the page.
Announcements
49
I have some tables that have relationships to each other over on Access. Since PowerApps does not have an Access connector I'm exporting them to Dataverse so I can use PowerApps as the front end. However the relationships between the tables always goes away. Is there a way to fix this? Can I create the relationships manually through Dataverse? I'm very new databases and PowerApps in general.
Hi @mbrown1 ,
The "Primary Name" field on every table in Dataverse is the primary key and in Dataverse you can add "lookup" columns to the child table that refers to the parent table to create a "1:N" relationship. Every time you create a table in Dataverse it will automatically create a column called "Name" as the primary column (although you can change this name of this field to be something that makes more sense for your situation).
Helpful links and video:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships
Example, I can create a table called Clinic that might have a number of fields but the "Primary Name" field is key when working with relationships to other tables.
Example, see the "Name" column where it says it is the Primary Name column below
Now, I have a Dental Order table that is related as a 1:N from the Clinic table identifying the clinic can have multiple Dental Orders. You will see I added a lookup column to Clinic in this table which is what effectively adds my 1:N relationship from the Clinic to the Dental Order.
You can then import data using Excel templates and if you set the Name of the Clinic on the import file when importing the Dental Orders and the name matches the Clinic Name field then it will create the relationship (note, the value of the name field must be unique on the Clinic for this approach, there are other ways to do this, let me know if this won't work).
Share
Report
All responses (
Answers (
