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

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

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 in the Forums 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**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Top Solution Authors
Top Kudoed Authors
Users online (2,143)