N:N relationship

(0) Share

Report

Posted on by PS10

I understand when to use 1:N or N:1 also N:N.

But say, if two entities A and B i create 1(A):N(B) later i feel the need to have opposite relationship 1(B):N(A), then my questoions are :

1) Is it okay to create the opposite relationship, any cons?

2) How is this 1:N and then N:1 on same set of entities be different from having a N:N relationship instead, should I have considered N:N in this kind of scenario, having N:N is good to have or not?

Thanks,

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

Abdul Wahab 12,119 Moderator on at

Like (1)

Report

RE: N:N relationship

Hi PS10,

Go with the N: N relationship instead of 1:N and N:1. But if somehow you need the 1:N and N:1 then use the key to make sure one of them is used as 1:1.

You can also create your custom N: N relationship by creating one more table.

If I answer your question then please mark it as verified.

Let me know if I can provide you with more details.

Thanks
Regards,

Abdul Wahab
Power Platform/Customer Engagement Developer/Lead/Solution Architecture/Project Manager
Direct/WhatsApp:+923323281237
E-mail: abdulwahabubit@outlook.com
Skype: abdul.wahabubit
Linkedin: www.linkedin.com/.../

Was this reply helpful? Yes No
PS10 8 on at

Like (0)

Report

RE: N:N relationship

Hi Abdul,

Thanks for your prompt reply.

Can you please explain more about the key and the option to use 1:1.

I definetly do not want to create a manul N:N.

Thanks,

PS

Was this reply helpful? Yes No
Verified answer

Abdul Wahab 12,119 Moderator on at

Like (1)

Report
RE: N:N relationship

Hi PS10,

Let's suppose you have two tables

Table A

Table B

For some reason, you created a 1:N relationship between Table A and Table B. In other words, you created a lookup column of Table A in Table B. Say this column to column A

Similarly, For some reason, you created a 1:N relationship between Table B and Table A. In other words, you created a lookup column of Table B in Table A. Say this column to column B

This is how you create an N: N relationship. To handle such a scenario. You need to create a key for Column A or column B. This you make this 1:Nto 1:1.

For more details read about keys, you need to read it out. The Key is unique. No one can duplicate it.

To create the key, you need to open your table from make.powerapps.com. Navigate to the key area.

If I answer your question then please mark it as verified.

Let me know if I can provide you with more details.

Thanks
Regards,

Abdul Wahab
Power Platform/Customer Engagement Developer/Lead/Solution Architecture/Project Manager
Direct/WhatsApp:+923323281237
E-mail: abdulwahabubit@outlook.com
Skype: abdul.wahabubit
Linkedin: www.linkedin.com/.../

Was this reply helpful? Yes No

Join the conversation

Community site session details

N:N relationship

Helpful resources

Quick Links

Responsible AI policies

Pallavi Phade – Community Spotlight

Congratulations to the October Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

N:N relationship

Helpful resources

Quick Links

Responsible AI policies

Pallavi Phade – Community Spotlight

Congratulations to the October Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates