One-To-Many relationship with same table

(0) Share

Report

Posted on by psreek

323

Hi,

I am trying to create a one-to-many relationship between records in the same table and dataverse converts that relationship into Many-To-One. How do I do this.

On clicking done, the relationship gets created as Many-to-one instead -

When I click the Edit button on the relationship, this now shows the reverse of what I had entered earlier during creation -

Any help is greatly appreciated.

regards

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

@prathyoo I think this is a result of the UI of the maker portal playing tricks. You have indeed created a one-to-many relationship. It's just the user interface that's only showing the relationship in the reverse direction. If you open your customisations in the classic experience, you'll be able to visual the relationship in both directions.

Was this reply helpful? Yes No
psreek 323 on at

Like (0)

Report

Hi,

As mentioned, the modern UI shows this -

But the classical UI shows two relationships - 1:N and N:1

The 1:N relationship looks like this -

The N:1 relationship looks like this -

I have no clue why the N:1 relationship exists as I needed 1:N relationship.

Now, when we try to show the Prior Events as a subgrid of the main Event form, we are able to associate an event to the parent event using "Add Existing Events"

But when we try to disassociate an event, such an option is not available but we only have Delete Event which seems to delete the main event record itself.

We get a feeling this has to be due to the way the relationship has been created by the studio.

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@prathyoo As the Name property of the relationship shows in the Classic experience, it's physically the same relationship component you're looking at from opposite directions: from the one-to-many end and then from the many-to-one end.

The sort of relationship essentially enables you to create child records that are related to a parent record. This is achieved by way of populating a lookup column on the child record which references the parent record. This lookup column is roughly the equivalent of a foreign key field in database terms.

If you open up a record in the Model Driven App, you should be able to see via the Associated View (or a subgrid on the form if you have configured it this way), all the child records associated to the parent. From the subgrid/associated view you should be able to open, view, edit or delete any of the child records (if you have permissions to do so as a user), using the corresponding buttons. The buttons on the main command bar relate to actions to be performed on the main record itself that you have opened.

You can disassociate a child record from it's parent record, by removing the value from the lookup column (foreign key), or you can associate it with another parent record by changing the value in this lookup column.

Was this reply helpful? Yes No