Relationships - Dataverse tables

(0) Share

Report

Posted on by sbroud

Hi Everyone,

I have two tables in Dataverse that have data (~5000 rows each.)

Is it possible to create relationship between these tables.

Person (PersonId, PersonName, PersonAddress, ServiceID)

Service (ServiceID, ServiceName, ServiceDepartment, ServiceCost)

Relationship : (Person.ServiceID <--> Service.ServiceID)

Issue found: Dataverse stops me when creating the relationship because the column already exists in the table.

Please help.

Thnak you in advance

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@sbroud Yes, you should be able to create the relationship your referring to.

Can you confirm what the Data Type is of the column called ServiceID on the Person table. If it is anything other than a Lookup that targets the Service table, you need to delete the existing column, and then re-create it as a Lookup column to target the Service table. This is effectively the foreign key which represents the one-to-many relationship you're referring to

Was this reply helpful? Yes No
ivan_apps 2,187 Moderator on at

Like (0)

Report

What kind of relationship are you trying to create? If a Person can have multiple Services and there can be multiple People per Service, it would be a many-to-many relationship (N:N). If a Person can have multiple services, but a Service can only have 1 Person, its a (1:N). If a Person can have only 1 Service, but a Service can have multiple People, its a (N:1).

You should not have a problem creating a N:N relationship because no lookup is created. An intersect table is created to handle the relationship.

If you are getting a 'column exists' issue, it is either a 1:N relationship or N:1 - verify you want one of these relationships. If you have created lookups in the past and called it 'ServiceID' then you already created a relationship by creating the lookup. Take a look at the 'relationships' list on the table to verify. If you need another similar relationship, you will simply have to call it something other than 'ServiceID' - something like 'ServiceID2' works just fine or something more descriptive.

Was this reply helpful? Yes No
365-Assist 2,324 Moderator on at

Like (0)

Report

If your ServiceID Column in the Person table is a lookup that looks up the Service ID in the Service Table then Dataverse automatically creates a relationship. And therefore you do not need to create another one.

Here is a sample I created.

This is the relationship it creates

---------------------------------------------------
Please Accept as Solution if it solves your question. Or just give it a Thumbs Up if it is helpful as can help others.

Subscribe: https://www.youtube.com/channel/UCFpvUlpx84FuIPOdInGKMTw

Regards
Darren Lutchner - 365 Assist

Was this reply helpful? Yes No