cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
lohaninarayan
Helper I
Helper I

Unable to filter and populate details to a table from collection

Hello all awesome people.

I believe I have a very basic problem but I can not get through it.

I have a form in edit mode and within the form, there is a table to display list of data from a SharePoint list.

Because the list have more than 2000 items and can not be delegated, I an trying to store data to a collection at app start.

The collection is loading the data but when I try to load the collection data to the table, it is coming empty.

Is there anything I am missing or simply PowerApps does not have that ability?

Any help will be appreciated.

Please check attached pics for more understanding.

I have already checked and there is data in the backend to match the condition and Tried to grab all fields or a single field but nothing worked.

lohaninarayan_0-1662531948918.png

lohaninarayan_1-1662532010414.png

lohaninarayan_2-1662532051007.png

 

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
poweractivate
Most Valuable Professional
Most Valuable Professional

@lohaninarayan 


I checked your issue more, and you are encountering multiple issues here.

First, the data table must be configured.

There are some steps to so this :

 

1. After adding the Data Table control to the Canvas App, select the Data Table Control, and then on the  very right side panel, under Properties tab, under "Fields", click on the purple text that says "Edit Fields"

2. On the flyout that shows up to the left of that panel, click "Add Field" that has the big plus symbol next to it.

poweractivate_0-1662544649560.png

 

3. In the small flyout that appears, check boxes for all the fields you want
4. and finally click the Add button.

poweractivate_7-1662545815452.png

 

 

You then get the result like this below

but you won't get that result like below with the Collection you have as-is, read on to see why )

poweractivate_3-1662544899099.png

 

However, the Table must not have any sub-tables for this to see those fields

 

Even if you do the above, you'll encounter an issue with your Data Table.

 

You must flatten your table as much as possible first, otherwise, you won't see any fields that are inside nested Tables or nested Collections!

For those items which have sub-tables, even if you check the box for it, like Incident or Role for example, they'll show up as [object Object] and not show anything else. They'll look like this, for example:

poweractivate_4-1662545034925.png

 

The above would be what happens when trying it on coll_02 in my example app - which I think is the closest to where your data is in level of transformation, since coll02 in my example ends up looking something like this:

 

poweractivate_6-1662545342647.png

There are two nested tables in my coll02, Incident and Role, kind of like your Incident and Role, each of which contain more than one record.

I have a custom example where I start with a very multi-dimensional table with nested tables in it, and that table itself is nested - and then I flatten it with multiple steps to turn it into a single table. The first step turns it into coll02 like above, because initially, the whole table is nested in just two readable records, both of which only show this in a Data Table control:

 

poweractivate_5-1662545254307.png

 

 

Here's the full example of how to turn that above, into this instead:

poweractivate_3-1662544899099.png



(I have a sample app later below in this post you can import, but here are the steps in case)

 

First, make a blank app with two blank screens, Screen1, and Screen2. Leave Screen2 blank.

 

Screen1 Onvisible:

 

 

ClearCollect(coll_original,[{id:0,Incident:[{logname:"123name",logid:"123"},{logname:"456name",logid:"456"}],Role:[{rolename:"123name",roleid:"123"},{rolename:"456name",roleid:"456"}]},{id:1,Incident:[{logname:"b123name",logid:"b123"},{logname:"b456name",logid:"b456"}],Role:[{rolename:"b123name",roleid:"b123"},{rolename:"b456name",roleid:"b456"}]}]);

ClearCollect(coll02, ForAll(Distinct(Ungroup(coll_original.Value,"Value"),ThisRecord.Value),Result));

ClearCollect(coll03, Ungroup(coll02,"Incident"));

ClearCollect(coll04, DropColumns(AddColumns(coll03,"logid",ThisRecord.Value.logid,"logname",ThisRecord.Value.logname),"Value"));

ClearCollect(coll05, Ungroup(coll04,"Role"));

ClearCollect(coll06, DropColumns(AddColumns(coll05,"roleid",ThisRecord.Value.roleid,"rolename",ThisRecord.Value.rolename),"Value"));

 

 

Toggle between Screen2 and Screen1 once.

 

Add your Data Table and select coll06 when prompted.

 

To experiment with Data Table fields and what shows on each stage, like for example to change it to coll_original, use the right side, and click Data Source, change it through that dropdown, and when prompted to replace columns, make sure to do so. You better don't change it by the formula bar Items directly.

 

Notice for coll_original, which is the original source collection, it's impossible to see any data at all:

poweractivate_5-1662545254307.png

 

 

Whereas with coll06, you see all the data. With the other collections, you have the ability to see incrementally more or less data depending where in the transformation it is.

 



Working Sample msapp

 

have attached a working (and revised) sample msapp file app31.msapp if you would like to import a full, working example yourself for your convenience.

 

To use the sample msapp attached, follow these steps:

 

1) Download the msapp file attached to this post (it's at the bottom of this post), to Desktop or a folder of your choice, by clicking on it from this post.

2) Create a new, blank Power App Canvas App

3) Go to File -> Open -> Browse

poweractivate_1-1662544680553.png

 

 

4 ) Navigate to location of .msapp file from Step 1, select it, and press the "Open" button.

5 ) The working example msapp file should load

6 ) Toggle between Screen2 and Screen1 once to initialize all the collections.
7 ) You can also check File -> Collections to see the Collections step by step as they are transformed.

8 ) You can try the full working example and also check the working formulas and setup as well in the app.


.

View solution in original post

poweractivate
Most Valuable Professional
Most Valuable Professional

@lohaninarayan 

 

Hello, I wanted to inform you that I tested it some more, and specifically with your Filter.

 

Your Filter will not work on your collection as is, because Incident is inside a nested table. Incident.Id simply does not even exist! The nested table causes the Incident Id you are looking for to be shadowed in Incident.Value and you may notice yourself the autocomplete won't even attempt to see what's inside Incident.Value .

 

In other words, "Incident.Value.Id" is an impossible thing to attempt to access. This is proper, correct behavior.  The Filter will only work correctly and be able to filter on incident id (which in my sample app, is most closely represented by "logid") after the whole Collection has been fully flattened first, and it probably should be flattened in a similar way as I gave in my initial response, all the way to coll06 in my response (you may also have success only flattening it up to coll04, where I have flattened the Incident, but not the Role).

 

If Incident is structured like in my sample app in your colPeopleInvolved collection, there may be more than one Incident id that corresponds to the outer table. So one row of your colPeopleInvolved actually has two, three, four, or who knows how many Incident Id's. In order for that to be properly checked, the data must be flattened so that the Filter would work as expected.

 

Power Apps doesn't even understand what's beyond Incident.Value in the first place, so it is unable to check what's really in there. The data has to be flattened first. Your attempt to look for Incident.Id won't succeed, because Incident is actually yet another Collection or Table, and it's actually Incident.Value

And Incident.Value is where it stops, so the Filter can't even be done.

 

You should flatten the data first, and then it would work, and I gave a detailed example about how to do it.

 

So in order to make sure your Filter works as intended, you should completely flatten the data first. 

 

Please check my response where I give the detailed instructions on how to configure the data table, how to flatten the data, and include a fully working sample app to try out yourself, and see if it helps @lohaninarayan 

View solution in original post

5 REPLIES 5
poweractivate
Most Valuable Professional
Most Valuable Professional

@lohaninarayan 

 

I'm not sure because I am checking it very quickly now, but it might be because there are collections nested within your collection such as Incident and Role. You may need to Ungroup (or flatten) them into another Collection with the columns expanded out from all the nested Collections. 

 

If this ends up being what you needed to do, here's some examples of doing this:

 

Aggregation nested collection

Ungroup record from collection 

Also you can check if this pattern works for you below as well (I did not test it):

 

ClearCollect(newColl,Ungroup(Ungroup(colPeopleInvolved,"Incident"),"Role");

//and finally use newColl and see if your data table likes it better

 

See if it helps @lohaninarayan 

poweractivate
Most Valuable Professional
Most Valuable Professional

@lohaninarayan 


I checked your issue more, and you are encountering multiple issues here.

First, the data table must be configured.

There are some steps to so this :

 

1. After adding the Data Table control to the Canvas App, select the Data Table Control, and then on the  very right side panel, under Properties tab, under "Fields", click on the purple text that says "Edit Fields"

2. On the flyout that shows up to the left of that panel, click "Add Field" that has the big plus symbol next to it.

poweractivate_0-1662544649560.png

 

3. In the small flyout that appears, check boxes for all the fields you want
4. and finally click the Add button.

poweractivate_7-1662545815452.png

 

 

You then get the result like this below

but you won't get that result like below with the Collection you have as-is, read on to see why )

poweractivate_3-1662544899099.png

 

However, the Table must not have any sub-tables for this to see those fields

 

Even if you do the above, you'll encounter an issue with your Data Table.

 

You must flatten your table as much as possible first, otherwise, you won't see any fields that are inside nested Tables or nested Collections!

For those items which have sub-tables, even if you check the box for it, like Incident or Role for example, they'll show up as [object Object] and not show anything else. They'll look like this, for example:

poweractivate_4-1662545034925.png

 

The above would be what happens when trying it on coll_02 in my example app - which I think is the closest to where your data is in level of transformation, since coll02 in my example ends up looking something like this:

 

poweractivate_6-1662545342647.png

There are two nested tables in my coll02, Incident and Role, kind of like your Incident and Role, each of which contain more than one record.

I have a custom example where I start with a very multi-dimensional table with nested tables in it, and that table itself is nested - and then I flatten it with multiple steps to turn it into a single table. The first step turns it into coll02 like above, because initially, the whole table is nested in just two readable records, both of which only show this in a Data Table control:

 

poweractivate_5-1662545254307.png

 

 

Here's the full example of how to turn that above, into this instead:

poweractivate_3-1662544899099.png



(I have a sample app later below in this post you can import, but here are the steps in case)

 

First, make a blank app with two blank screens, Screen1, and Screen2. Leave Screen2 blank.

 

Screen1 Onvisible:

 

 

ClearCollect(coll_original,[{id:0,Incident:[{logname:"123name",logid:"123"},{logname:"456name",logid:"456"}],Role:[{rolename:"123name",roleid:"123"},{rolename:"456name",roleid:"456"}]},{id:1,Incident:[{logname:"b123name",logid:"b123"},{logname:"b456name",logid:"b456"}],Role:[{rolename:"b123name",roleid:"b123"},{rolename:"b456name",roleid:"b456"}]}]);

ClearCollect(coll02, ForAll(Distinct(Ungroup(coll_original.Value,"Value"),ThisRecord.Value),Result));

ClearCollect(coll03, Ungroup(coll02,"Incident"));

ClearCollect(coll04, DropColumns(AddColumns(coll03,"logid",ThisRecord.Value.logid,"logname",ThisRecord.Value.logname),"Value"));

ClearCollect(coll05, Ungroup(coll04,"Role"));

ClearCollect(coll06, DropColumns(AddColumns(coll05,"roleid",ThisRecord.Value.roleid,"rolename",ThisRecord.Value.rolename),"Value"));

 

 

Toggle between Screen2 and Screen1 once.

 

Add your Data Table and select coll06 when prompted.

 

To experiment with Data Table fields and what shows on each stage, like for example to change it to coll_original, use the right side, and click Data Source, change it through that dropdown, and when prompted to replace columns, make sure to do so. You better don't change it by the formula bar Items directly.

 

Notice for coll_original, which is the original source collection, it's impossible to see any data at all:

poweractivate_5-1662545254307.png

 

 

Whereas with coll06, you see all the data. With the other collections, you have the ability to see incrementally more or less data depending where in the transformation it is.

 



Working Sample msapp

 

have attached a working (and revised) sample msapp file app31.msapp if you would like to import a full, working example yourself for your convenience.

 

To use the sample msapp attached, follow these steps:

 

1) Download the msapp file attached to this post (it's at the bottom of this post), to Desktop or a folder of your choice, by clicking on it from this post.

2) Create a new, blank Power App Canvas App

3) Go to File -> Open -> Browse

poweractivate_1-1662544680553.png

 

 

4 ) Navigate to location of .msapp file from Step 1, select it, and press the "Open" button.

5 ) The working example msapp file should load

6 ) Toggle between Screen2 and Screen1 once to initialize all the collections.
7 ) You can also check File -> Collections to see the Collections step by step as they are transformed.

8 ) You can try the full working example and also check the working formulas and setup as well in the app.


.

poweractivate
Most Valuable Professional
Most Valuable Professional

@lohaninarayan 

Let's suppose you don't care about Incident and Role for colPeopleInvolved, and only want to use those for the Filter itself.

In that case, you can attempt to avoid the flattening in my example altogether, especially if you don't want any of the fields in the nested tables, to be actually inside of the data table. but you should still select the correct non-nested fields to test it, and just try it first without the Filter. Just use colPeopleInvolved for the Items property of the Data Table. Better yet, save your Filter formula somewhere if you need to have it handy, just delete the Data Table Control and just add a new one. When prompted, just select colPeopleInvolved when it shows up.

 

As an initial test, I suggest you try it without the Filter, just have the Data Table on the whole colPeopleInvolved and just try to select the fields in the Steps 1-4 I give in the first part of my response (particularly try to select the fields that don't have a nested table, the fields with a nested table will just show [object Object] if you use colPeopleInvolved as-is) and just see if it even works then and shows something. If it does, then the problem may be with your Filter, and/or because the data has not been flattened, or some other issue. 

 

You can also use completely custom data cards, or just unlock the data cards where you get a roadblock (e.g. Incident) and attempt to get nested data by modifying the datacard itself rather than flatten the data and expose it in a way that results in a built-in datacard. However, this may be rather complex and non-intuitive. Manipulating datacards or using custom datacards might not be an adequate substitute for flattening the data first, so I don't recommend manipulating the data cards, and instead recommend flattening the data where you need direct access to fields inside of a "nested" table.

poweractivate
Most Valuable Professional
Most Valuable Professional

@lohaninarayan 

 

Hello, I wanted to inform you that I tested it some more, and specifically with your Filter.

 

Your Filter will not work on your collection as is, because Incident is inside a nested table. Incident.Id simply does not even exist! The nested table causes the Incident Id you are looking for to be shadowed in Incident.Value and you may notice yourself the autocomplete won't even attempt to see what's inside Incident.Value .

 

In other words, "Incident.Value.Id" is an impossible thing to attempt to access. This is proper, correct behavior.  The Filter will only work correctly and be able to filter on incident id (which in my sample app, is most closely represented by "logid") after the whole Collection has been fully flattened first, and it probably should be flattened in a similar way as I gave in my initial response, all the way to coll06 in my response (you may also have success only flattening it up to coll04, where I have flattened the Incident, but not the Role).

 

If Incident is structured like in my sample app in your colPeopleInvolved collection, there may be more than one Incident id that corresponds to the outer table. So one row of your colPeopleInvolved actually has two, three, four, or who knows how many Incident Id's. In order for that to be properly checked, the data must be flattened so that the Filter would work as expected.

 

Power Apps doesn't even understand what's beyond Incident.Value in the first place, so it is unable to check what's really in there. The data has to be flattened first. Your attempt to look for Incident.Id won't succeed, because Incident is actually yet another Collection or Table, and it's actually Incident.Value

And Incident.Value is where it stops, so the Filter can't even be done.

 

You should flatten the data first, and then it would work, and I gave a detailed example about how to do it.

 

So in order to make sure your Filter works as intended, you should completely flatten the data first. 

 

Please check my response where I give the detailed instructions on how to configure the data table, how to flatten the data, and include a fully working sample app to try out yourself, and see if it helps @lohaninarayan 

Hi @poweractivate 

 

Thanks for the reply and all examples you have posted.

I have managed to fix the issue with the help of your examples. However, ended up creating different connection;

col1. get the desired list with delegable filter

col2. added new column with incident object value

col3. added new column with role object value

col4. dropped column incident and role object

 And I was able to use col4 to display on my table.

My question to you is, is there a shorter script to have less collections?

I am marking your post as solution because it helped me solve the issue.

 

Thanks

Narayan

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Tuesday Tips: Community Ranks and YOU

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!This Week: Community Ranks--Moving from "Member" to "Community Champion"   Have you ever wondered how your fellow community members ascend the ranks within our community? What sets apart an Advocate from a Helper, or a Solution Sage from a Community Champion? In today’s #TuesdayTip, we’re unveiling the secrets and sharing tips to help YOU elevate your ranking—and why it matters to our vibrant communities. Community ranks serve as a window into a member’s role and activity. They celebrate your accomplishments and reveal whether someone has been actively contributing and assisting others. For instance, a Super User is someone who has been exceptionally helpful and engaged. Some ranks even come with special permissions, especially those related to community management. As you actively participate—whether by creating new topics, providing solutions, or earning kudos—your rank can climb. Each time you achieve a new rank, you’ll receive an email notification. Look out for the icon and rank name displayed next to your username—it’s a badge of honor! Fun fact: Your Community Engagement Team keeps an eye on these ranks, recognizing the most passionate and active community members. So shine brightly with valuable content, and you might just earn well-deserved recognition! Where can you see someone’s rank? When viewing a post, you’ll find a member’s rank to the left of their name.Click on a username to explore their profile, where their rank is prominently displayed. What about the ranks themselves? New members start as New Members, progressing to Regular Visitors, and then Frequent Visitors.Beyond that, we have a categorized system: Kudo Ranks: Earned through kudos (teal icons).Post Ranks: Based on your posts (purple icons).Solution Ranks: Reflecting your solutions (green icons).Combo Ranks: These orange icons combine kudos, solutions, and posts. The top ranks have unique names, making your journey even more exciting! So dive in, collect those kudos, share solutions, and let’s see how high you can rank! 🌟 🚀   Check out the Using the Community boards in each of the communities for more helpful information!  Power Apps, Power Automate, Copilot Studio & Power Pages

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

Top Solution Authors
Top Kudoed Authors
Users online (6,904)