Kinh Nghiệm Hướng dẫn SharePoint lists many to many relationship Chi Tiết
You đang tìm kiếm từ khóa SharePoint lists many to many relationship được Update vào lúc : 2022-01-16 12:15:09 . Với phương châm chia sẻ Mẹo về trong nội dung bài viết một cách Chi Tiết 2022. Nếu sau khi Read Post vẫn ko hiểu thì hoàn toàn có thể lại Comments ở cuối bài để Ad lý giải và hướng dẫn lại nha.
How to giảm giá with many to many relationships in Dataverse
- by: Luise FreeseNov 18, 2022
While building an app that stores data in Dataverse, I came across a not easy to resolve problem. If you already follow me for a bit longer, you may assume that this is about ProvisionGenie, and so I will use this use case of provisioning Microsoft Teams teams and storing data about that as an example. To explain the issue, we first need to understand some basics, which I will cover here first:
Nội dung chính
- How to giảm giá with many to many relationships in DataverseWhat is DataverseHow does Dataverse distinguish from SharePoint lists and what makes it a real database?What kind of relationships do exist in Dataverse?1-to-many relationshipMany-to-many relationshipsHow can you reference Many-to-Many Relationships in Azure Logic Apps?Luise FreeseYou May Also Likebe brave enough to suck something newHow to move your blog from WordPress to HugoHow 3 makers, 2 devs and a princess came together to save kittens for a hackathonVideo liên quan
What is Dataverse
Dataverse is a is a secure and scalable SaaS data service, that sits right in Power Platform. Datverses database is Azure SQL, and often, people refer to Dataverse just as a database, but it is so much more:
I will not go into full detail in this blog post, but cover something that people with a background in Microsoft 365/SharePoint might not be aware of:
How does Dataverse distinguish from SharePoint lists and what makes it a real database?
In Dataverse, we store data in tables, we can either use predefined ones or we can creates our own tables. We can choose from different kind of column types to store data just as needed. The beautiful thing that get our Dynamics 365 colleagues excited is, that Dataverse can serve as a relational database, which means that we can create all kinds of relationships between data, which gives us a better overview on data as we can put data into context.
Also, we have role-based access control (RBAC), which means that we can granularly control who can view, edit, delete etc. data, while this isnt possible with SharePoint lists. If we use a list as data source for a Power Apps, we need to share the entire list with all users of that application, which means that users can even bypass the app and manipulate and delete data directly on the SharePoint site.
Now you may ask, what is it about relationships in Dataverse that makes it so special?
What kind of relationships do exist in Dataverse?
1-to-many relationship
In a 1:N (1-to-many) relationship we associate a (1) row of a table to many other rows in a related table with a lookup column. We can see a list of the related rows that are associated with our primary table.
You will come across the term N:1(many-to-1) as well – it is the same thing as a 1:N relationship- just viewed from the related table, not from the parent/primary table.
As an example, please imagine a table Teams Requests and another related table Teams Channels. Each Team can have many channels, but a channel can be only associated with one Team (represented in the Teams Request table). This means, that we need to have a 1:N relationship between Teams Requests table and the Teams Channels table. We reference this like this:
We get the correct environment, fetch the table Team Channels and filter by TeamsRequestId so that only the related channels to that Teams request will be returned.
Many-to-many relationships
An N:N (many-to-many) relationship depends on a special relationship table (intersect table), so that many rows of one table can be related to many rows of another table.
We can see a list of all rows in the related table that our primary table is associated with.
As an example, please image now the Teams Requests table again that needs to be related to a Teams Users table. In this Teams Users table we want to store information on members and owners of the teams in the Teams Requests table.
A Teams can have many users as members, and each user can be a thành viên of different Teams.
Also, a team can have many users as owners and these users can be owners of several different teams.
This means, that we need to have two N:N relationships between teams Requests table and Teams Users table.
Now the intersection tables come into play: They make sure that we can associate many rows of the related table to the primary table.
In Dataverse, we dont get to see these intersection tables. but we can customize their name:
How can you reference Many-to-Many Relationships in Azure Logic Apps?
Now that the distinguishing element between an Owner of a Team and a Member of that Team is in the relationship, we need to reference that intersection table in a Logic App flow in order to fetch the right rows from the Teams User table to add them with the correct role to the Team that we want to provision.
In order to do so, we select the correct environment, and type the name of the relationship table followed by a set, then we filter for the correct Teams Request ID so that only members for that specific team will be returned.
The very same applies to the relationship table for the owners.
Conclusion
Before you build your Power Platform solution, its absolutely worth it to spend a couple of thoughts on the data model. If you
- need more relationships than a simple lookup columnneed granular control who can access which rowsa performant place to store dataa highly scalable solution
then its very likely, that Dataverse is a service that you should consider.
In order to take full advantage of Dataverses capabilities in terms of being a relational database its worth it to understand what is an intersection table and how you can reference it. Let me know what you think in the comments
Please enable JavaScript to view the comments powered by Disqus.comments powered by DisqusAbout Me
My name is
Luise Freese
Microsoft 365 Consultant, Low Code Dev, Microsoft MVP for Office Apps & Services and thành viên of M365 PnP team, based in Germany.. Read MoreRecent Post
- be brave enough to suck something newDec 27, 2022How to move your blog from WordPress to HugoDec 18, 2022How 3 makers, 2 devs and a princess came together to save kittens for a hackathonOct 23, 2022
Categories
- Adaptive cards 8Azure 4Community 18Consultant life 33Dev 36Lego 1Microsoft 365 49Microsoft graph 15Mindset 7Mobile 2Power platform 30Productivity 27Sketchnotes 3Speaking 4
Tags
- CommunityConsultantlifeDevDigital workplaceM365pnpMicrosoft 365Office 365PnpRecapStickers
You May Also Like
be brave enough to suck something new
Tis the season where we all look back to reflect what happened in the
- by: LuiseDec 27, 2022
How to move your blog from WordPress to Hugo
If you are a little bit like me, you started to blog some years ago on
- by: LuiseDec 18, 2022
How 3 makers, 2 devs and a princess came together to save kittens for a hackathon
How 3 makers, 2 devs and a princess came together to save kittens for
- by: LuiseOct 23, 2022
- YouTubeTwitterInstagramGitHubLinkedIn
Subscribe to my newsletter.
Copyright ©2022
Reply
9
0
Chia sẻ
Clip SharePoint lists many to many relationship ?
Bạn vừa đọc nội dung bài viết Với Một số hướng dẫn một cách rõ ràng hơn về Review SharePoint lists many to many relationship tiên tiến và phát triển nhất
Chia Sẻ Link Download SharePoint lists many to many relationship miễn phí
Bạn đang tìm một số trong những Share Link Cập nhật SharePoint lists many to many relationship miễn phí.
Hỏi đáp vướng mắc về SharePoint lists many to many relationship
Nếu You sau khi đọc nội dung bài viết SharePoint lists many to many relationship , bạn vẫn chưa hiểu thì hoàn toàn có thể lại Comment ở cuối bài để Mình lý giải và hướng dẫn lại nha
#SharePoint #lists #relationship