Afternoon all. I was wondering if someone could help.
I am trying to get ALL teams a user is a member of and their membership role (owner or member).
At the moment, I am using 2 different Graph API calls
Owner
https://graph.microsoft.com/v1.0/users/{0}/ownedObjects
Member
https://graph.microsoft.com/v1.0/users/{0}/memberOf
Using the above solution I get 2 json objects.
I have used Select to create the following for ownership
{
"body": [
{
"id": "1645466-et65-5h556-5645-45645646456",
"displayName": "SZ BMW",
"role": "owner"
},
{
"id": "123456-et65-5hh6-45645-45645646456",
"displayName": "NR Jon Snow",
"role": "owner"
}
]
}
... and for member
{
"body": [
{
"id": "1645466-et65-5h556-5645-45645646456",
"displayName": "SZ BMW",
"role": "member"
},
{
"id": "567567-et65-5666-4665-456477777456",
"displayName": "UK Members Only",
"role": "member"
},
{
"id": "123456-et65-5hh6-45645-45645646456",
"displayName": "NR Jon Snow",
"role": "member"
}
]
}
Based on the above, I am trying to create a joined list which shows their owner status and if an item in the member does not exist in owners, add it as below
{
"body": [
{
"id": "1645466-et65-5h556-5645-45645646456",
"displayName": "SZ BMW",
"role": "owner" <=============
},
{
"id": "567567-et65-5666-4665-456477777456",
"displayName": "UK Members Only",
"role": "member" <=============
},
{
"id": "123456-et65-5hh6-45645-45645646456",
"displayName": "NR Jon Snow",
"role": "owner" <=============
}
]
}
So I have 2 questions.
1. Is there another, easier way to recreate the above?
2. Could someone help me with the filter/join based on the above?
Thank you in advance
Solved! Go to Solution.
Hi @jimbobuk,
Yes, no problem. Here is step-by-step walkthrough. Btw, the screenshots should be clickable (which should open a dialog with a clearer picture).
1. Add a Initialize variable action
a. Provide a name, OwnerandMemberArray
b. Select Array Type
c. In Value use []
2. Add a second Initialize variable action
a. Provide a name, MembershipArray
b. Select Array Type
c. In Value use []
3. Add a Get User Profile (v2) action
a. use the email of the user for which you want to lookup the memberships
4. Add a Send an HTTP request (Office 365 Groups connector action)
a. Rename action to Send an HTTP request - ownedObjects
b. Use the following URI
https://graph.microsoft.com/v1.0/users/@{outputs('Get_user_profile_(V2)')?['body/id']}/ownedObjects/?$select=id,displayName
5. Add a Select action
a. Rename action to Select - ownedObjects
b. Use the following expression in From
body('Send_an_HTTP_request_-_ownedObjects')['value']
c. Switch map to text mode and use the following expression
item()['id']
6. Add an Apply to Each action
a. Rename action to Apply to each - ownedObjects
a. Use the following expression in the Select an output from previous steps field
body('Send_an_HTTP_request_-_ownedObjects')['value']
7. Add an append to Array variable action (within Apply to each - ownedObjects)
a. Select the MembershipArray
b. Use the following value
{"id":"@{item()['id']}","displayName":"@{item()['displayName']}","role":"owner"}
8. Add a Send an HTTP request (Office 365 Groups connector action)
a. Rename action to Send an HTTP request - memberOf
b. Use the following URI
https://graph.microsoft.com/v1.0/users/@{outputs('Get_user_profile_(V2)')?['body/id']}/memberOf/?$select=id,displayName,role
9. Add a Select action
a. Rename action to Select - memberOf
b. Use the following expression in From
body('Send_an_HTTP_request_-_memberOf')['value']
c. Switch map to text mode and use the following expression
item()['id']
10. Add a Set Variable action
a. Select the OwnerandMemberArray
b. Use the expression below for the Value field
intersection(body('Select_-_ownedObjects'),body('Select_-_memberOf'))
11. Add an Apply to Each action
a. Rename action to Apply to each - memberOf
a. Use the following expression in the Select an output from previous steps field
body('Send_an_HTTP_request_-_memberOf')['value']
12. Add a Filter Array action (within Apply to each - memberOf)
a. Use the OwnerandMemberArray variable in the From
b. Click Edit in advanced mode and add the following expression
@equals(item(), items('Apply_to_each_-_memberOf')['id'])
13. Add a Condition action (within Apply to each - memberOf)
a. Use the following check
length(body('Filter_array'))
is equal to 0
14. Add a Append to array variable (within Apply to each - memberOf, in the If yes of the Condition)
a. Rename action to Append to array variable - memberOf
b. Select the MembershipArray
c. Add the following to the Value field
{"id":"@{item()['id']}","displayName":"@{item()['displayName']}","role":"member"}
Hi @jimbobuk,
With the current setup you could use an array variable and append the results of both queries to that array.
Below is an example of that approach.
1. I used a MembershipArray variable.
2. The value of the ownedObjects request is used in an apply to each.
3. Within the apply to each the results are append via the following json:
{"id":"@{item()['id']}","displayName":"@{item()['displayName']}","role":"owner"}
4. For the memberOf results use the same variable and append to approach.
The end result should be one variable which contains all memberships for one specific user.
Hi and thanks for such a quick reply.
The above is a great solution but doesnt get me to where I want to be with regards to membership.
If you notice, some of the member roles have the same id as those in owner role.
Ideally, I would like to keep all the owner role entries and emit/discard member roles where the id is the same
Thanks again!
Hi @jimbobuk,
In that case I would use two additional select actions to only retrieve the ids from both responses.
You can use an intersection function to match the ids of those two arrays.
Within the memberof Apply to each loop you can use a filter array to see if the id of the current item matches that intersection output.
If it cannot find a match for the group id (by using a length equals 0 expression) it is only a member of the group and you can append it to the variable.
Below is a quick screenshot of such a setup. Let me know if you need more details.
I guess my code is incorrect. I am trying to follow your steps but the images are not too clear!
Any chance you could send me a copy of the flow?
Thank you!
Hi @jimbobuk,
Yes, no problem. Here is step-by-step walkthrough. Btw, the screenshots should be clickable (which should open a dialog with a clearer picture).
1. Add a Initialize variable action
a. Provide a name, OwnerandMemberArray
b. Select Array Type
c. In Value use []
2. Add a second Initialize variable action
a. Provide a name, MembershipArray
b. Select Array Type
c. In Value use []
3. Add a Get User Profile (v2) action
a. use the email of the user for which you want to lookup the memberships
4. Add a Send an HTTP request (Office 365 Groups connector action)
a. Rename action to Send an HTTP request - ownedObjects
b. Use the following URI
https://graph.microsoft.com/v1.0/users/@{outputs('Get_user_profile_(V2)')?['body/id']}/ownedObjects/?$select=id,displayName
5. Add a Select action
a. Rename action to Select - ownedObjects
b. Use the following expression in From
body('Send_an_HTTP_request_-_ownedObjects')['value']
c. Switch map to text mode and use the following expression
item()['id']
6. Add an Apply to Each action
a. Rename action to Apply to each - ownedObjects
a. Use the following expression in the Select an output from previous steps field
body('Send_an_HTTP_request_-_ownedObjects')['value']
7. Add an append to Array variable action (within Apply to each - ownedObjects)
a. Select the MembershipArray
b. Use the following value
{"id":"@{item()['id']}","displayName":"@{item()['displayName']}","role":"owner"}
8. Add a Send an HTTP request (Office 365 Groups connector action)
a. Rename action to Send an HTTP request - memberOf
b. Use the following URI
https://graph.microsoft.com/v1.0/users/@{outputs('Get_user_profile_(V2)')?['body/id']}/memberOf/?$select=id,displayName,role
9. Add a Select action
a. Rename action to Select - memberOf
b. Use the following expression in From
body('Send_an_HTTP_request_-_memberOf')['value']
c. Switch map to text mode and use the following expression
item()['id']
10. Add a Set Variable action
a. Select the OwnerandMemberArray
b. Use the expression below for the Value field
intersection(body('Select_-_ownedObjects'),body('Select_-_memberOf'))
11. Add an Apply to Each action
a. Rename action to Apply to each - memberOf
a. Use the following expression in the Select an output from previous steps field
body('Send_an_HTTP_request_-_memberOf')['value']
12. Add a Filter Array action (within Apply to each - memberOf)
a. Use the OwnerandMemberArray variable in the From
b. Click Edit in advanced mode and add the following expression
@equals(item(), items('Apply_to_each_-_memberOf')['id'])
13. Add a Condition action (within Apply to each - memberOf)
a. Use the following check
length(body('Filter_array'))
is equal to 0
14. Add a Append to array variable (within Apply to each - memberOf, in the If yes of the Condition)
a. Rename action to Append to array variable - memberOf
b. Select the MembershipArray
c. Add the following to the Value field
{"id":"@{item()['id']}","displayName":"@{item()['displayName']}","role":"member"}
Perfect! Thank you so much!
Could I ask where you learnt Power Automate? Do you have any links etc as I would like to take some training!
Thanks again
Hi @jimbobuk,
Personally I just learned it from projects, reading the docs, following blogs, watching videos and helping out in these forums.
I would start with the Microsoft Self-pace learning modules:
If that is not sufficient you can always have a look at third-party training companies.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages