cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
LRVinNC
Resident Rockstar
Resident Rockstar

Question about On Visible after Back()

OK gurus of PowerApps -- need your wisdom once again.

Details:

  • Data source is a Sharepoint list.
  • Screen1 has a very complex On Visible event that builds a collection used to display a report in a gallery on Screen 1.  
  • User can click on a detail line in the report on Screen 1 and be taken to the edit form for the selected item in Screen 2. 
  • User makes a changes to the item on the edit form in Screen 2 and a submit form posts the change.  The On Success fires for the form which executes a Back(), displaying Screen 1 again.
  • All is well EXCEPT that the change made in the edit form is not being reflected in the gallery on Screen 1. 
  • I tried using a Navigate to return to Screen 1 instead of a Back and the result was the same.
  • I also tried issuing a refresh on the SP list I updated prior to doing the Back and the result was the same.
  • If I try to re-edit the same item, I get an item not found on Screen 2 because I am matching on the text to find the correct item in the SP list that matches the item in the collection. (This is what I would expect to happen).  If I cancel out of Screen 2 (which executes a ResetForm then a Back), the data in the gallery IS in fact refreshed.  

 

Questions:

  • Isn't the On Visible supposed to fire each time Screen 1 becomes visible?  
  • Do I need to also patch the collection with the change at the same time I process the Submit form?  I would not have expected to do this as I would have thought the On Visible would simply rebuild with the latest information when I did the Back.
  • What else can I do to insure the gallery reflects the change when I return to Screen 1?

Thanks in advance!

LRVinNC

------------------
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
1 ACCEPTED SOLUTION

Accepted Solutions

LO AND BEHOLD - after MUCH wailing and gnashing of teeth - I figured out what the problem was.  I was right!  There was no problem with my code.  The problem was an experimental app setting I had turned on, thinking it sounded like a good idea.  NOT!  At least not for this app.  The problem child was "Use longer data cache timeout and background refresh."  As soon as I turned it off, things started working correctly.  Even a forced refresh prior to the collection load appeared to be ignored which caused the data to be incorrect in the collection.  

LRVinNC

------------------
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

View solution in original post

4 REPLIES 4
RandyHayes
Super User
Super User

@LRVinNC 

Questions:

Isn't the On Visible supposed to fire each time Screen 1 becomes visible? 

Yes, and it does.  I would reinvestigate that you don't have something that is causing it NOT to execute.  A conditional statement, an error in the actual formula, etc.

 

Do I need to also patch the collection with the change at the same time I process the Submit form?  I would not have expected to do this as I would have thought the On Visible would simply rebuild with the latest information when I did the Back.

Depends - if you are NOT going to refresh and rebuild the collection after you submit or alter the datasource, then you will need to submit and alter the collection at the same time.  

What you expect is correct...if the OnVisible is rebuilding the collection, then you need not add to the collection.

 

What else can I do to insure the gallery reflects the change when I return to Screen 1?

Double check that you are not conditionally excluding the OnVisible actions.  Also, for tests, consider setting a variable in the OnVisible like : UpdateContext({aNumber: aNumber+1}) then putting a label on the screen with aNumber as its text property.

 

I hope this helps lead to a revelation.

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

I can find no conditionals or errors which would prevent the update.  I have used a label to verify that the On Visible IS being invoked -- but the collection is NOT being updated when returning from the update on Screen 2.  I have tried forcing a refresh of the list when leaving Screen 2, but Screen 1 still does not update.  I have tried returning to Screen 1 with a Navigate rather than a Back, but Screen 1 still does not update.  Yet when I exit from Screen 1 to the Home Page and invoke Screen 1 again, it DOES update. 

Here's the On Visible code:

Set(
    RptPopUpVisible,
    false
);
Set(StartDate,DateAdd(dpWeekEndDate.SelectedDate,-6));
Clear(multiList);
// Skeleton structure of what is about to happen:
//
//  ForAll(shaped and grouped Data, 
//         collect-departments into multiList; 
//         ForAll(projects in department groups, 
//                collect-projects into multiList; 
//                ForAll(stones in project groups, 
//                       collect-Accomp into multiList
//                      )
//               )
//        )
ForAll(
    //We need to group two levels - one for the inner accomplishments grouped by Department and Project (records are the (Accomp)lishments)
    //We need to compare a few things in the later levels, so we also need to add the department and project in the 
    // appropriate places - this will speed up the lookups in the ForAlls
    SortByColumns(
        GroupBy(
            SortByColumns(
                AddColumns(
                    GroupBy(
                        AddColumns(
                            SortByColumns(
                                Filter(
                                    PA,
                                    Archive = false
                                ),
                                "Title"
                            ),//Sort the list so Accomplishments (PA) are in order
                            "dep",
                            DepartmentName.Value,
                            "proj",
                            ProjectName.Value
                        ),//AddColumns - Put the dep and proj on the records of all milestones
                        "dep",
                        "proj",
                        "accomp"
                    ),// LEVEL 2 GroupBy - group by the department and project and give us a table of accomp
                    "depL2",
                    dep
                ),// AddColumns add the department at LEVEL 2 as well (but a different name)
                "proj"
            ),// SortBy Project Column
            "depL2",
            "Projects"
        ),// LEVEL 1 GroupBy - finally group by the Department with a table of projects
        "depL2"
    ),// SortByColumns - Sort by Department Column
    //The stage is set....Now lets collect some records 
    // DEPARTMENTS
    // Here we are on the outside of the groups - we have a Department column and a table column of Project Records
    // REMEMBER: we are in a ForAll function - this is the FIRST statement of the ForAll...a Collect function
    Collect(
        multiList,
         //Every record in our final collection should have a DataLevel (used only during this compilation, a DepLevel, which is the caclulated Department
         //level, a Project Level - a calculation of the project level, and a milestonelevel - also calculated
        {
            DataLevel: 1,
            // we use the datalevel for our filter statements only, this is level 1
            DeptLevel: CountRows(Filter(multiList, DataLevel = 1)) + 1,
            //count the number of rows in our collection that are at this datalevel, we should be the next one
            ProjLevel: 0,
            // we're at the department level now, so all records have 0 project
            PALevel: 0,
            // we're at the department level now, so all records have 0 PA
            myDept: depL2,
            //and of course, the real data...the department name at this point is all we care about
            sortKey: Text(CountRows(Filter(multiList, DataLevel = 1))+ 1,"[$-en-US]000")  & "000" & "000"
        }
    );
    
    // PROJECTS      
    // Now lets collect with the Departments' Projects - here we go into the Projects tables of the group
    // REMEMBER: we are in a ForAll function - this is the SECOND (and last) statement of the outer ForAll...this final statement is a ForAll 
    // Here we are working with the Projects table column from the outer group LEVEL 1
ForAll(
        Projects,
        Collect(
            multiList,
            {
                DataLevel: 2,
                // we use the datalevel for our filter statements only, this is level 2
                DeptLevel: LookUp(multiList, myDept = dep).DeptLevel,
                // in this level, we look up the department level for this department that was collected before
                ProjLevel: CountRows(Filter(multiList, DataLevel = 2)) + 1,
                // count the number of rows in our collection that are at this datalevel, we are the next one
                PALevel: 0,
                //we're at the project level now, so 0 PA
                myDept: depL2,
                //and of course, the real data...the department name
                myProject: proj,
                // and the project name
                sortKey: Text(LookUp(multiList, myDept = dep).DeptLevel,"[$-en-US]000") & Text(CountRows(Filter(multiList, DataLevel = 2)) + 1,"[$-en-US]000") & "000"
            }
        );
        Collect(
            multiList,
            {
                DataLevel: 3,
                // we use the datalevel for our filter statements only, this is level 2
                DeptLevel: LookUp(multiList, myDept = depL2).DeptLevel,
                // in this level, we look up the department level for this department that was collected before
                ProjLevel: CountRows(Filter(multiList,DataLevel = 2)), // we look up the project level for this project that was collected before
                PALevel: 1,        //we're at the project level now, so 0 PA
                myDept: depL2,     //and of course, the real data...the department name
                myProject: proj,   // and the project name
                PA: "Accomplishments",
                PAType: " ",
                sortKey: Text(LookUp(multiList,myDept = depL2).DeptLevel,"[$-en-US]000") & Text(CountRows(Filter(multiList, DataLevel = 2)),"[$-en-US]000") & "001"
            }
        );
        
        // ACCOMPLISHMENTS        
        // we are in the Projects grouping...so let's grab the Accomp as well now
        // REMEMEBER: We are the second statement in the Last statement of the outer ForAll
        // Here we are working with the Accomp table column from the inner group LEVEL 2
ForAll(
            Projects[@accomp],
            Collect(
                multiList,
                {
                    DataLevel: 3,   // we use the datalevel for our filter statements only, this is level 3
                    DeptLevel: LookUp(multiList, myDept = dep).DeptLevel,  // in this level, we look up the department level for this department that was collected before
                    ProjLevel: CountRows(Filter(multiList, DataLevel = 2)),
                    // we look up the project level for this project that was collected before
                    //now count the rows that are associated with the dept and proj - we are the next one.
                    PALevel: CountRows(Filter(multiList, myDept = depL2 && myProject = proj && DataLevel = 3)),
                    // And finally, all the real data that we need for the final list
                    myDept: depL2,
                    myProject: proj,
                    PA: Title,
                    PAD: AdditionalDetail,
                    PAType: "A",
                    RptDate: StatusDate,
                    ID: ID,
                    sortKey: Text(LookUp(multiList, myDept = dep).DeptLevel,"[$-en-US]000") & Text(CountRows(Filter(multiList, DataLevel = 2)),"[$-en-US]000") & 
                             Text(CountRows(Filter(multiList, myDept = depL2 && myProject = proj && DataLevel = 3)),"[$-en-US]000")
                }
            )//end of accomp Collect 
        )// end of accomp ForAll          
    )// end of Projects ForAll
);
// end of grouped ForAll
//REPEAT THE ENTIRE PROCESS FOR NEXT STEPS BUT ONLY WRITE OUT THE NEXT STEPS HEADER AND DATALEVEL 3 RECORDS
    //We need to group two levels - one for the inner next steps grouped by Department and Project (records are the Steps)
    //We need to compare a few things in the later levels, so we also need to add the department and project in the 
    // appropriate places - this will speed up the lookups in the ForAlls
ForAll(
    SortByColumns(
        GroupBy(
            SortByColumns(
                AddColumns(
                    GroupBy(
                        AddColumns(
                            SortByColumns(
                                Filter(
                                    NextSteps,
                                    Archive = false
                                ),
                                "Title"
                            ),//Sort the list so NextSteps are in order
                            "dep",
                            DepartmentName.Value,
                            "proj",
                            ProjectName.Value
                        ),//AddColumns - Put the dep and proj on the records of all NextSteps
                        "dep",
                        "proj",
                        "Steps"
                    ),// LEVEL 2 GroupBy - group by the department and project and give us a table of Steps
                    "depL2",
                    dep
                ),// AddColumns add the department at LEVEL 2 as well (but a different name)
                "proj"
            ),// SortBy Project Column
            "depL2",
            "Projects"
        ),// LEVEL 1 GroupBy - finally group by the Department with a table of projects
        "depL2"
    ),// SortByColumns - Sort by Department Column
    //The stage is set....Now lets collect some records 
    // PROJECTS      
    // Now lets collect with the Departments' Projects - here we    go into the Projects tables of the group
    // REMEMBER: we are in a ForAll function - this is the SECOND (and last) statement of the outer ForAll...this final statement is a ForAll 
    // Here we are working with the Projects table column from the outer group LEVEL 1
    ForAll(
        Projects,
        Collect(
            multiList,
            {
                DataLevel: 3,
                // we use the datalevel for our filter statements only, this is level 2
                DeptLevel: LookUp(multiList,myDept = depL2).DeptLevel,
                // in this level, we look up the department level for this department that was collected before
                ProjLevel: LookUp(multiList, myDept = depL2 && myProject = proj && DataLevel = 2).ProjLevel,
                // we look up the project level for this project that was collected before
                PALevel: CountRows(Filter(multiList, myDept = depL2 && myProject = proj && DataLevel = 3)),
                //we're at the project level now, so 0 PA
                myDept: depL2,
                //and of course, the real data...the department name
                myProject: proj,
                // and the project name
                PA: "Next Week",
                PAType: " ",
                sortKey: Text(LookUp(multiList, myDept = depL2).DeptLevel,"[$-en-US]000") & 
                         Text(LookUp(multiList, myDept = depL2 && myProject = proj && DataLevel = 2).ProjLevel,"[$-en-US]000") & 
                         Text(CountRows(Filter(multiList, myDept = depL2 && myProject = proj && DataLevel = 3)),"[$-en-US]000")
            }
        );
        
        // NEXT STEPS/NEXT WEEK        
        // we are in the Projects grouping...so let's grab the Steps as well now
        // REMEMEBER: We are the second statement in the Last statement of the outer ForAll
        // Here we are working with the Steps table column from the inner group LEVEL 2
ForAll(
            Projects[@Steps],
            Collect(
                multiList,
                {
                    DataLevel: 3,
                    // we use the datalevel for our filter statements only, this is level 3
                    DeptLevel: LookUp(multiList, myDept = dep).DeptLevel,
                    // in this level, we look up the department level for this department that was collected before
                    ProjLevel: LookUp(multiList, myDept = depL2 && myProject = proj && DataLevel = 2).ProjLevel,
                    // we look up the project level for this project that was collected before
                     //now count the rows that are associated with the dept and proj - we are the next one.
                    PALevel: CountRows(Filter(multiList,myDept = depL2 && myProject = proj && DataLevel = 3)),
                     // And finally, all the real data that we need for the final list
                    myDept: depL2,
                    myProject: proj,
                    PA: Title,
                    PAD: AdditionalDetails,
                    PAType: "N",
                    RptDate: StatusDate, 
                    ID: ID,
                    sortKey: Text(LookUp(multiList, myDept = dep).DeptLevel,"[$-en-US]000") & 
                             Text(LookUp(multiList, myDept = depL2 && myProject = proj && DataLevel = 2).ProjLevel,"[$-en-US]000") & 
                             Text(CountRows(Filter(multiList, myDept = depL2 && myProject = proj && DataLevel = 3)),"[$-en-US]000")
                }
            )//end of Steps Collect 
        )// end of Steps ForAll          
    )// end of Projects ForAll
);
// end of Group ForAll

The OnSelect that applies the update on screen 2 is:

Patch(Audit,Defaults(Audit),{Title:"Next Steps",UpdateDate:Now(),DepartmentName:{Id:LookUp(Department, Dept in Title,ID),
Value: Dept,'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference"},
ProjectName:{Id:LookUp(Projects, Proj in Title,ID),
Value: Proj,'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference"}});
SubmitForm(EditNext);Patch(Department,First( Filter( Department, Title = Dept ) ), { DataLastUpdt: Today() } )

And the Success event for the form is simply:
OS2.png

I just can't find anything that should be  causing this to occur...

LRVinNC

------------------
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

@LRVinNC 

That is some crazy formula you've got there...how did you come up with something that crazy? LOL  (for those observing this message - we collaborated on this through some private messages 😉 )

 

So, you are saying that your testing by adding a variable to the OnVisible did in fact update properly, but the multiList collection is NOT getting updated?  So from the Patch function and the datasource from the EditForm, you are patching and updating NextSteps and Audit datasources.  

In your formula, the first "build" of the multiList is entirely based on the PA datasource.  I'm suspicious about the second "amendment" to the multiList that is based on the NextSteps datasource.

My suspicion is that something in that NextSteps part is not executing as expected...or really, that it is, but not yielding what you might think.

It's rather difficult to troubleshoot this one without the data and sample, so, I can provide some suggestions...

1) Add some time stamp columns in multList - dTime : Now()

    Check those immediately after page OnVisible in the Collection viewer.  They should update each time.

2) Pull the second NextSteps part out of the formula completely and see if there is a change (in the collection...I expect there would be in your app).  Same for the first part based on PA.

 

Other considerations...personally I would pull this entire formula out of the OnVisible property and put it in its own place.  It seems the two formulas, for PA and for NextSteps, can stand on their own apart from each other (not sure on this...you know your data better) because they both feed new items to multList.

I would put the formulas in a Toggle control's OnCheck property and use a variable to "fire" the building of the collection when needed (ex. in OnVisible, or after a form is submitted etc.) This would give you much greater control of that formula and would move it into some place easier to troubleshoot.

Just some suggestions.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

LO AND BEHOLD - after MUCH wailing and gnashing of teeth - I figured out what the problem was.  I was right!  There was no problem with my code.  The problem was an experimental app setting I had turned on, thinking it sounded like a good idea.  NOT!  At least not for this app.  The problem child was "Use longer data cache timeout and background refresh."  As soon as I turned it off, things started working correctly.  Even a forced refresh prior to the collection load appeared to be ignored which caused the data to be incorrect in the collection.  

LRVinNC

------------------
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

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! 💪🌠

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)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Top Solution Authors
Top Kudoed Authors
Users online (5,893)