cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
PowerApps11
Post Patron
Post Patron

The best way Patch

Hi,
I wanted to put my app on to production but am still not confident to do it the reason is my patching is it correct or what is the best way to use it and better for performance wise also, at moment here is example my patch and it is working but takes time on run had to wait a bit? possible to improve performance and time shorten code? 

Set(gblTaskLS,
Patch(
        TaskLS,
        If(gblRecordState,
           Defaults(TaskLS),
           gblTaskLS),
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes:DataCardValue13.Text
        }
    ));
Patch(
        NotesTaskLS,
        Defaults(NotesTaskLS),
        {
            Title: gblTaskLS.Title,
            Due: gblTaskLS.Due,
            TransType: DataCardValue12.Selected.Value,
            Notes: gblTaskLS.Notes
        }
    ));
Patch(
        IssuesTaskLS,
        Defaults(IssuesTaskLS),
        {
            Title: gblTaskLS.Title,
            Due: gblTaskLS.Due,
            TransType: DataCardValue12.Selected.Value,
            IssueType: DataCardValue13.Selected.Value,
            Notes: gblTaskLS.Notes
        }
    ));
// and two more lists 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
poweractivate
Super User
Super User

@PowerApps11 

 

Example

 

Instead of

 

Patch(
        TaskLS,
        If(gblRecordState,
           Defaults(TaskLS),
           gblTaskLS),
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes:DataCardValue13.Text
        }
    ));

 

Write it like this instead

 

Patch
(
     TaskLS,
     {
         ID:If(gblRecordState,Blank(),gblTaskLS.ID),
         Title: DataCardValue7.Text,
         Due: DataCardValue4.SelectedDate,
         TransType: DataCardValue12.Selected.Value,
         Notes:DataCardValue13.Text
     }
)

 

If the above has any issue, it may not like when you try to Patch in Blank() values, check if turning on the formula-level error management setting helps with this?

 

1. Click Settings

2. Click Upcoming Features

3. Toggle the Formula-level error management setting to On

Then just close the modal, see if it works.

 

poweractivate_0-1664838760107.png

 

The idea of putting the If statement inside the ID value is so that you don't have to use Defaults, and don't have to re-declare the entire record. When the ID is Blank, a new record is created anyway, using what you already provided, whereas if the ID is not blank, what you provided will be used to modify the existing record with the primary key given (ID). In SharePoint List, the ID column is the primary key column, so use the ID to identify a record uniquely for Patch.

 

Try to use this above guideline in rewriting your other parts of the formula.

See if it helps @PowerApps11 

View solution in original post

poweractivate
Super User
Super User

@PowerApps11 If you still have slowdown after applying the above, I suspect it may be how you have done the app in general. For example, that fact that you set gblTaskLS and have the Patch functions inside may be indicative that you're doing it in a way that could be causing slowdowns. You could try and not use the variable at all and see if it helps. This may be difficult to do since you may be depending on the result of this variable currently.

 

If the above changes to Patch do not work, try eliminating your use of the Set function and eliminate the use of the variable entirely to see if something you're doing with the variable is causing a slowdown. It may be difficult for you to do this because it depends what you're trying to accomplish exactly. 

 

For example, if it's as simple as Patching directly from the datacards again directly to each List, try doing exactly that and don't use the variable at all.

 

//elsehwere in your app, have gblRecord just be the specific TaskLS record you want to change, or set it to Blank() if it should not be set at that moment.
Patch
(
        TaskLS,
        {
            ID: If(!IsBlank(gblRecord),gblRecord.ID,Blank())
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes:DataCardValue13.Text
        }
    
);
If
(
    !IsBlank(gblRecord)
   ,Patch
   (
        NotesTaskLS,
        {
            Title: gblRecord.Title,
            Due: gblRecord.Due,
            TransType: DataCardValue12.Selected.Value,
            Notes: gblRecord.Notes
        }
    
   );
   Patch
   (
        IssuesTaskLS,
        {
            Title: gblRecord.Title,
            Due: gblRecord.Due,
            TransType: DataCardValue12.Selected.Value,
            IssueType: DataCardValue13.Selected.Value,
            Notes: gblRecord.Notes
        }
   )
)

 

See if this might help as well. The above version eliminates 2 unnecessary patch calls for new records

 

or try this version if you need to create everything even when it's a new Record - just reference the data cards yet again, it might be better that way:

 

//elsehwere in your app, have gblRecord just be the specific TaskLS record you want to change, or set it to Blank() if it should not be set at that moment.
Patch
(
        TaskLS,
        {
            ID: If(!IsBlank(gblRecord),gblRecord.ID,Blank())
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes:DataCardValue13.Text
        }
    
);

Patch
(
        NotesTaskLS,
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes: DataCardValue13.Text
        }
    
);
Patch
(
        IssuesTaskLS,
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            IssueType: DataCardValue13.Selected.Value, //???
            Notes: DataCardValue13.Text
        }
   )
)

 

In the above version, it raises some questions:

1. Why do you need to duplicate values across so many lists?

2. IssueType for IssuesTaskLS says DataCardValue13.Selected.Value which was in your original formula as well, but earlier in the same Patch sequence it was DataCardValue13.Text - why is that? The form can only be one or the other for DataCardValue13, right? So there may be an actual error there or the possibility for there to be one.

 

I think the duplication of the data across many Lists, especially with all Lists you provided appearing to have essentially almost identical schema and receiving almost identical data may be a sign that you should model the data differently on the SharePoint List side. If you need to duplicate everything so much, then you may be using Patch calls to multiple Lists unnecessarily, causing the slowdown also unnecessarily.  If that's the case then for what you need to do differently, that really depends what you actually want to do.

I am not sure the purpose of your given Lists TaskLS, NotesTaskLS, and IssuesTaskLS - they seem like duplicates of the same thing from the Patch formulas you provided, so I don't understand their purpose at all in the first place just from what you provided.

Just based on just what you provided I'd just remove all the other Lists and use just TaskLS, and then not Patch to any other List to make less Patch calls since I don't see a purpose for those Lists based on what you provided.

However, maybe those other Lists you are using do have a purpose - perhaps they have other columns that are important to you as well.

If so, then you might need to provide detail on a high level what exactly do you want to do?

 

I'd recommend modeling something like this

Instead of duplicating all the fields again, keep an ID of which TaskLS it is. Wait - you don't have to - it already has an ID out of the box!

Instead of duplicating the same columns and data in NotesTaskLS and IssuesTaskLS, just have one column called TaskLSID - or TaskID - or something like that - inside both Lists, and in it you can patch the ID of the TaskLS which contains the other information you need. Then you can always lookup the ID of the TaskLS even directly from NotesTaskLS and IssuesTaskLS.

 

However, this only makes sense if NotesTaskLS and IssuesTaskLS actually have any other columns at all to begin with besides the ones in TaskLS.

 

If NotesTaskLS and IssuesTaskLS really had no other columns, besides the same ones in TaskLS that you are trying to duplicate all the time in your Patch formulas to NotesTaskLS and IssuesTaskLS  as you gave them - then just delete these Lists altogether and don't bother patching to them, only patch to TaskLS then!

 

Similarly, you could just move all columns from NotesTaskLS and IssuesTaskLS  directly to TaskLS then remove both Lists NotesTaskLS and IssuesTaskLS

 

 

By the way, I wasn't sure if you were going to have more than one NotesTaskLS per TaskLS Record and more than one IssuesTaskLS per TaskLS Record.

 

If so, then these Patch statements don't look right at all, and the data model of your SharePoint Lists also does not look correct currently.

 

If you were trying to really do that (i.e. have one or more NotesTaskLS Records associated with a single TaskLS Record) you'll need to do something like what I was saying where you have a column called TaskID, so NotesTaskLS might have a TaskID column for example. So now zero, one, or more than one NotesTaskLS Records may have a TaskID that is the same across multiple  NotesTaskLS Records. So from any one NotesTaskLS you can always look up which specific TaskLS Record it is associated with using

 

LookUp(TaskLS,ID=myCurrentNoteRecord.TaskID)

 

If not associated with any Record, this above LookUp returns Blank(). If it is associated with a record, it always returns exactly one Record.

 

To get all the multiple NotesTaskLS attached to a particular TaskLS you can do this then: 

 

Filter(NotesTaskLS,TaskID=myCurrentTaskRecord.ID)

 

to get a Table of associated NotesTaskLS by the TaskLS Record's ID. 

When there are no matches, the Table should be Empty

 

And when you Patch to NotesTaskLS you should remember on new record creation to specify for TaskID column which Task it is (i.e. specify which record of TaskLS it is by its ID), so that later you can LookUp a Task from a Note, or use Filter to get all the Notes attached to a single Task.

 

See if it helps @PowerApps11 

View solution in original post

7 REPLIES 7
poweractivate
Super User
Super User

@PowerApps11 

The best way is to always use only 2 arguments to Patch, like this:

//To update an existing record
Patch
(
   YourDataSource
   {
       ID: YourID //PRIMARY KEY
       Field1: YourField1Contents
       Field2: YourField2Contents
   }
)

//To create a new record
Patch
(
   YourDataSource
   {
       //OMIT the primary key - leave it out - to create a new record
       Field1: YourField1Contents
       Field2: YourField2Contents
   }
)

See if it helps @PowerApps11 

poweractivate
Super User
Super User

@PowerApps11 

 

Example

 

Instead of

 

Patch(
        TaskLS,
        If(gblRecordState,
           Defaults(TaskLS),
           gblTaskLS),
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes:DataCardValue13.Text
        }
    ));

 

Write it like this instead

 

Patch
(
     TaskLS,
     {
         ID:If(gblRecordState,Blank(),gblTaskLS.ID),
         Title: DataCardValue7.Text,
         Due: DataCardValue4.SelectedDate,
         TransType: DataCardValue12.Selected.Value,
         Notes:DataCardValue13.Text
     }
)

 

If the above has any issue, it may not like when you try to Patch in Blank() values, check if turning on the formula-level error management setting helps with this?

 

1. Click Settings

2. Click Upcoming Features

3. Toggle the Formula-level error management setting to On

Then just close the modal, see if it works.

 

poweractivate_0-1664838760107.png

 

The idea of putting the If statement inside the ID value is so that you don't have to use Defaults, and don't have to re-declare the entire record. When the ID is Blank, a new record is created anyway, using what you already provided, whereas if the ID is not blank, what you provided will be used to modify the existing record with the primary key given (ID). In SharePoint List, the ID column is the primary key column, so use the ID to identify a record uniquely for Patch.

 

Try to use this above guideline in rewriting your other parts of the formula.

See if it helps @PowerApps11 

poweractivate
Super User
Super User

@PowerApps11 

 

For these 

 

Patch(
        NotesTaskLS,
        Defaults(NotesTaskLS),
        {
            Title: gblTaskLS.Title,
            Due: gblTaskLS.Due,
            TransType: DataCardValue12.Selected.Value,
            Notes: gblTaskLS.Notes
        }
    ));
Patch(
        IssuesTaskLS,
        Defaults(IssuesTaskLS),
        {
            Title: gblTaskLS.Title,
            Due: gblTaskLS.Due,
            TransType: DataCardValue12.Selected.Value,
            IssueType: DataCardValue13.Selected.Value,
            Notes: gblTaskLS.Notes
        }
    ));

 

Rewrite these as 

 

Patch(
        NotesTaskLS,
        {
            Title: gblTaskLS.Title,
            Due: gblTaskLS.Due,
            TransType: DataCardValue12.Selected.Value,
            Notes: gblTaskLS.Notes
        }
    ));
Patch(
        IssuesTaskLS,
        {
            Title: gblTaskLS.Title,
            Due: gblTaskLS.Due,
            TransType: DataCardValue12.Selected.Value,
            IssueType: DataCardValue13.Selected.Value,
            Notes: gblTaskLS.Notes
        }
    ));
poweractivate
Super User
Super User

@PowerApps11 If you still have slowdown after applying the above, I suspect it may be how you have done the app in general. For example, that fact that you set gblTaskLS and have the Patch functions inside may be indicative that you're doing it in a way that could be causing slowdowns. You could try and not use the variable at all and see if it helps. This may be difficult to do since you may be depending on the result of this variable currently.

 

If the above changes to Patch do not work, try eliminating your use of the Set function and eliminate the use of the variable entirely to see if something you're doing with the variable is causing a slowdown. It may be difficult for you to do this because it depends what you're trying to accomplish exactly. 

 

For example, if it's as simple as Patching directly from the datacards again directly to each List, try doing exactly that and don't use the variable at all.

 

//elsehwere in your app, have gblRecord just be the specific TaskLS record you want to change, or set it to Blank() if it should not be set at that moment.
Patch
(
        TaskLS,
        {
            ID: If(!IsBlank(gblRecord),gblRecord.ID,Blank())
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes:DataCardValue13.Text
        }
    
);
If
(
    !IsBlank(gblRecord)
   ,Patch
   (
        NotesTaskLS,
        {
            Title: gblRecord.Title,
            Due: gblRecord.Due,
            TransType: DataCardValue12.Selected.Value,
            Notes: gblRecord.Notes
        }
    
   );
   Patch
   (
        IssuesTaskLS,
        {
            Title: gblRecord.Title,
            Due: gblRecord.Due,
            TransType: DataCardValue12.Selected.Value,
            IssueType: DataCardValue13.Selected.Value,
            Notes: gblRecord.Notes
        }
   )
)

 

See if this might help as well. The above version eliminates 2 unnecessary patch calls for new records

 

or try this version if you need to create everything even when it's a new Record - just reference the data cards yet again, it might be better that way:

 

//elsehwere in your app, have gblRecord just be the specific TaskLS record you want to change, or set it to Blank() if it should not be set at that moment.
Patch
(
        TaskLS,
        {
            ID: If(!IsBlank(gblRecord),gblRecord.ID,Blank())
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes:DataCardValue13.Text
        }
    
);

Patch
(
        NotesTaskLS,
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes: DataCardValue13.Text
        }
    
);
Patch
(
        IssuesTaskLS,
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            IssueType: DataCardValue13.Selected.Value, //???
            Notes: DataCardValue13.Text
        }
   )
)

 

In the above version, it raises some questions:

1. Why do you need to duplicate values across so many lists?

2. IssueType for IssuesTaskLS says DataCardValue13.Selected.Value which was in your original formula as well, but earlier in the same Patch sequence it was DataCardValue13.Text - why is that? The form can only be one or the other for DataCardValue13, right? So there may be an actual error there or the possibility for there to be one.

 

I think the duplication of the data across many Lists, especially with all Lists you provided appearing to have essentially almost identical schema and receiving almost identical data may be a sign that you should model the data differently on the SharePoint List side. If you need to duplicate everything so much, then you may be using Patch calls to multiple Lists unnecessarily, causing the slowdown also unnecessarily.  If that's the case then for what you need to do differently, that really depends what you actually want to do.

I am not sure the purpose of your given Lists TaskLS, NotesTaskLS, and IssuesTaskLS - they seem like duplicates of the same thing from the Patch formulas you provided, so I don't understand their purpose at all in the first place just from what you provided.

Just based on just what you provided I'd just remove all the other Lists and use just TaskLS, and then not Patch to any other List to make less Patch calls since I don't see a purpose for those Lists based on what you provided.

However, maybe those other Lists you are using do have a purpose - perhaps they have other columns that are important to you as well.

If so, then you might need to provide detail on a high level what exactly do you want to do?

 

I'd recommend modeling something like this

Instead of duplicating all the fields again, keep an ID of which TaskLS it is. Wait - you don't have to - it already has an ID out of the box!

Instead of duplicating the same columns and data in NotesTaskLS and IssuesTaskLS, just have one column called TaskLSID - or TaskID - or something like that - inside both Lists, and in it you can patch the ID of the TaskLS which contains the other information you need. Then you can always lookup the ID of the TaskLS even directly from NotesTaskLS and IssuesTaskLS.

 

However, this only makes sense if NotesTaskLS and IssuesTaskLS actually have any other columns at all to begin with besides the ones in TaskLS.

 

If NotesTaskLS and IssuesTaskLS really had no other columns, besides the same ones in TaskLS that you are trying to duplicate all the time in your Patch formulas to NotesTaskLS and IssuesTaskLS  as you gave them - then just delete these Lists altogether and don't bother patching to them, only patch to TaskLS then!

 

Similarly, you could just move all columns from NotesTaskLS and IssuesTaskLS  directly to TaskLS then remove both Lists NotesTaskLS and IssuesTaskLS

 

 

By the way, I wasn't sure if you were going to have more than one NotesTaskLS per TaskLS Record and more than one IssuesTaskLS per TaskLS Record.

 

If so, then these Patch statements don't look right at all, and the data model of your SharePoint Lists also does not look correct currently.

 

If you were trying to really do that (i.e. have one or more NotesTaskLS Records associated with a single TaskLS Record) you'll need to do something like what I was saying where you have a column called TaskID, so NotesTaskLS might have a TaskID column for example. So now zero, one, or more than one NotesTaskLS Records may have a TaskID that is the same across multiple  NotesTaskLS Records. So from any one NotesTaskLS you can always look up which specific TaskLS Record it is associated with using

 

LookUp(TaskLS,ID=myCurrentNoteRecord.TaskID)

 

If not associated with any Record, this above LookUp returns Blank(). If it is associated with a record, it always returns exactly one Record.

 

To get all the multiple NotesTaskLS attached to a particular TaskLS you can do this then: 

 

Filter(NotesTaskLS,TaskID=myCurrentTaskRecord.ID)

 

to get a Table of associated NotesTaskLS by the TaskLS Record's ID. 

When there are no matches, the Table should be Empty

 

And when you Patch to NotesTaskLS you should remember on new record creation to specify for TaskID column which Task it is (i.e. specify which record of TaskLS it is by its ID), so that later you can LookUp a Task from a Note, or use Filter to get all the Notes attached to a single Task.

 

See if it helps @PowerApps11 

Hi @poweractivate 
Thank you for you clear information , you right some of the patch statements was just copy not the actual the one using, wanted to know why taking time for the patching, put it looks as you said no need to use defaults that helped the speed also below helped me thank you so much.

ID: If(gblRecordState,Blank(),gblTaskLS.ID)

For sure you made me understand how to use patch correctly.
@poweractivate  in the come days will create new thread asking the best way to use ForAll and how to add ForAll a variable to reuse it like get all ID's just patched ForAll and attached them on to another list like notes.

Do you mind if I tag you?

 


@PowerApps11 wrote:

Hi @poweractivate 
ForAll and how to add ForAll a variable to reuse it like get all ID's just patched ForAll and attached them on to another list like notes.

Do you mind if I tag you?

 


You may tag me.

If you do not use the output table of ForAll, try not to use it at all.

Try not to use ForAll as a for loop.

In general use ForAll inside Patch,    do not use ForAll outside of Patch,

In general use Patch outside ForAll,  do not use Patch inside ForAll

it's better to Patch just once on a whole Table,

than patch multiple times inside a ForAll whose outer table is never being used.

 

You may give a specific example if you want of your use of ForAll so I can check it, the above advice may be hard to apply sometimes.

 

Here is a general advice I have for using Patch outside ForAll:

//usually bad
ForAll
(
   Patch
   (
      //BAD
   )
)

//usually good
Patch
(
   ForAll
   (
      //GOOD
   )
)

 

@poweractivate 
Yes I use 

Patch
(
   ForAll
   (
      //GOOD
   )
)

But hard to find how can I add variable inside the ForAll so I can reuse it and get the id's just just patched ForAll
for example my case 

Patch
NotesTaskLS,
ForAll(galMulti.AllItems,
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            Notes: DataCardValue13.Text
        }
    
);
Patch
(
        IssuesTaskLS,
        {
            Title: DataCardValue7.Text,
            Due: DataCardValue4.SelectedDate,
            TransType: DataCardValue12.Selected.Value,
            IssueType: DataCardValue13.Selected.Value,
            TaskLSID: xxxxx.ID // i want the id of the NotesTaskLS
            Notes: DataCardValue13.Text
        }
   )
)

Is that looks right for you? or I need to do differently please?

Helpful resources

Announcements

Back to Basics: Tuesday Tip #1: All About YOUR Community Account

We are excited to kick off our new #TuesdayTIps series, "Back to Basics." This weekly series is our way of helping the amazing members of our community--both new members and seasoned veterans--learn and grow in how to best engage in the community! Each Tuesday, we will feature new areas of content that will help you best understand the community--from ranking and badges to profile avatars, from Super Users to blogging in the community. Our hope is that this information will help each of our community members grow in their experience with Power Platform, with the community, and with each other!     This Week's Tips: Account Support: Changing Passwords, Changing Email Addresses or Usernames, "Need Admin Approval," Etc.Wondering how to get support for your community account? Check out the details on these common questions and more. Just follow the link below for articles that explain it all.Community Account Support - Power Platform Community (microsoft.com)   All About GDPR: How It Affects Closing Your Community Account (And Why You Should Think Twice Before You Do)GDPR, the General Data Protection Regulation (GDPR), took effect May 25th 2018. A European privacy law, GDPR imposes new rules on companies and other organizations offering goods and services to people in the European Union (EU), or that collect and analyze data tied to EU residents. GDPR applies no matter where you are located, and it affects what happens when you decide to close your account. Read the details here:All About GDPR - Power Platform Community (microsoft.com)   Getting to Know You: Setting Up Your Community Profile, Customizing Your Profile, and More.Your community profile helps other members of the community get to know you as you begin to engage and interact. Your profile is a mirror of your activity in the community. Find out how to set it up, change your avatar, adjust your time zone, and more. Click on the link below to find out how:Community Profile, Time Zone, Picture (Avatar) & D... - Power Platform Community (microsoft.com)   That's it for this week. Tune in for more Tuesday Tips next Tuesday and join the community as we get "Back to Basics."

Power Platform Community Newsletter: September 2023

Welcome to our September 2023 Newsletter, where we highlight the latest news, product releases, podcasts, upcoming events, and the great work of our Power Platform Community members. As usual, please make sure you follow our News & Announcements in the Community to stay up to date. Another great way to connect is to join our Power Platform Community on LinkedIn. You can join our LInkedIn community here.   MPPC's Got Power - Submissions end September 28th! Are you ready to showcase your skills at the Microsoft Power Platform Conference in Las Vegas? Don't miss out on the "MPPC's Got Power" talent show, a grand celebration of connection, inspiration, and shared journeys. Whether you're a technical innovator, a talented storyteller, or have a hidden creative side, we want to see what you've got! With three categories to choose from, you have the chance to shine on stage and make your mark in the Microsoft Power Platform community.  Click the GIF to sign up by Thursday 28th September to be part of an unforgettable MPPC23 experience. Now is your time to shine!     Check Out the Low Code Approach Podcast Give the Low Code Approach Podcast a listen! Hosted by Sean Fiene, Wendy Haddad, and Kenric Auguillard, this innovative show shines a light on how Microsoft MVPs, product team members, and Community users are building exciting solutions using Microsoft Power Platform. Plus, with guests like Kartik Kanakasabesan, April Dunnam, Ricardo Duncan Jr., Sonja Gu, Phil Topness, Shane Young and more, this weekly show is a must for all you Business Applications enthusiasts out there. Click the image below to check it out!           COMMUNITY HIGHLIGHTS Check out the most active Community users for August 2023. These hardworking members are posting regularly, answering questions, writing blogs, giving kudos, and providing top solutions in their communities across Power Platform. Huge thanks to these amazing community members for their great contributions last month! trice602poweractivateLaurensMWarrenBelzAmikBCBuizerSamLedcreativeopinion timlExpiscornovusManishSolankiMattJimisonfernandosilvaMisterMarkPstork1saudali_25hafizsultan242Lucas001ragavanrajanp_doc   UPCOMING EVENT: 365 EDUCON CHICAGO Whether you're new to Microsoft 365, Power Platform and SharePoint, or an experienced power user, admin or developer, 365 EduCon has content designed to fit your experience level and area of interest. Their workshops and sessions are taught by Microsoft Certified Trainers, MVPs, Regional Directors, and Engineers. Find out more and register here: Home - Microsoft 365 EduCon Chicago - A Microsoft 365 Conference.  

Announcing the MPPC's Got Power Talent Show at #MPPC23

Are you attending the Microsoft Power Platform Conference 2023 in Las Vegas? If so, we invite you to join us for the MPPC's Got Power Talent Show!      Our talent show is more than a show—it's a grand celebration of connection, inspiration, and shared journeys. Through stories, skills, and collective experiences, we come together to uplift, inspire, and revel in the magic of our community's diverse talents. This year, our talent event promises to be an unforgettable experience, echoing louder and brighter than anything you've seen before.    We're casting a wider net with three captivating categories:  Demo Technical Solutions: Show us your Power Platform innovations, be it apps, flows, chatbots, websites or dashboards... Storytelling: Share tales of your journey with Power Platform. Hidden Talents: Unveil your creative side—be it dancing, singing, rapping, poetry, or comedy. Let your talent shine!    Got That Special Spark? A Story That Demands to Be Heard? Your moment is now!  🚀 Sign up to Showcase Your Brilliance: https://aka.ms/MPPCGotPowerSignUp  🔥 Deadline for submissions: Thursday, Sept 28th    How It Works:  Submit this form to sign up: https://aka.ms/MPPCGotPowerSignUp  We'll contact you if you're selected. Get ready to be onstage!  The Spotlight is Yours: Each participant has 3-5 minutes to shine, with insightful commentary from our panel of judges. We’re not just giving you a stage; we’re handing you the platform to make your mark.     Be the Story We Tell: Your talents and narratives will not just entertain but inspire, serving as the bedrock for our community’s future stories and successes.    Celebration, Surprises, and Connections: As the curtain falls, the excitement continues! Await surprise awards and seize the chance to mingle with industry experts, Microsoft Power Platform leaders, and community luminaries. It's not just a show; it's an opportunity to forge connections and celebrate shared successes.    Event Details:  📆 Date and Time: Wed Oct 4th, 6:30-9:00PM   📍 Location: MPPC23 at the MGM Grand, Las Vegas, NV, USA  

September User Group Success Story: Reading Dynamics 365 & Power Platform User Group

The Reading Dynamics 365 and Power Platform User Group is a community-driven initiative that started in September 2022. It has quickly earned recognition for its enthusiastic leadership and resilience in the face of challenges. With a focus on promoting learning and networking among professionals in the Dynamics 365 and Power Platform ecosystem, the group has grown steadily and gained a reputation for its commitment to its members!   The group, which had its inaugural event in January 2023 at the Microsoft UK Headquarters in Reading, has since organized three successful gatherings, including a recent social lunch. They maintain a regular schedule of four events per year, each attended by an average of 20-25 enthusiastic participants who enjoy engaging talks and, of course, pizza.     The Reading User Group's presence is primarily spread through LinkedIn and Meetup, with the support of the wider community. This thriving community is managed by a dedicated team consisting of Fraser Dear, Tim Leung, and Andrew Bibby, who serves as the main point of contact for the UK Dynamics 365 and Power Platform User Groups.   Andrew Bibby, an active figure in the Dynamics 365 and Power Platform community, nominated this group due to his admiration for the Reading UK User Group's efforts. He emphasized their remarkable enthusiasm and success in running the group, noting that they navigated challenges such as finding venues with resilience and smiles on their faces. Despite being a relatively new group with 20-30 members, they have managed to achieve high attendance at their meetings.   The group's journey began when Fraser Dear moved to the Reading area and realized the absence of a user group catering to professionals in the Dynamics 365 and Power Platform space. He reached out to Andrew, who provided valuable guidance and support, allowing the Reading User Group to officially join the UK Dynamics 365 and Power Platform User Groups community.   One of the group's notable achievements was overcoming the challenge of finding a suitable venue. Initially, their "home" was the Microsoft UK HQ in Reading. However, due to office closures, they had to seek a new location with limited time. Fortunately, a connection with Stephanie Stacey from Microsoft led them to Reading College and its Institute of Technology. The college generously offered them event space and support, forging a mutually beneficial partnership where the group promotes the Institute and encourages its members to support the next generation of IT professionals.   With the dedication of its leadership team, the Reading Dynamics 365 and Power Platform User Group is poised to continue growing and thriving! Their story exemplifies the power of community-driven initiatives and the positive impact they can have on professional development and networking in the tech industry. As they move forward with their upcoming events and collaborations with Reading College, the group is likely to remain a valuable resource for professionals in the Reading area and beyond.

A Celebration of What We've Achieved--And Announcing Our Winners

As the sun sets on the #SummerofSolutions Challenge, it's time to reflect and celebrate! The journey we embarked upon together was not just about providing answers – it was about fostering a sense of community, encouraging collaboration, and unlocking the true potential of the Power Platform tools.   From the initial announcement to the final week's push, the Summer of Solutions Challenge has been a whirlwind of engagement and growth. It was a call to action for every member of our Power Platform community, urging them to contribute their expertise, engage in discussions, and elevate collective knowledge across the community as part of the low-code revolution.   Reflecting on the Impact As the challenge ends, it's essential to reflect on the impact it’s had across our Power Platform communities: Community Resilience: The challenge demonstrated the resilience of our community. Despite geographical distances and diverse backgrounds, we came together to contribute, learn, and collaborate. This resilience is the cornerstone of our collective strength.Diverse Expertise: The solutions shared during the challenge underscore the incredible expertise within our community. From intricate technical insights to creative problem-solving, our members showcased their diverse skill sets, enhancing our community's depth.Shared Learning: Solutions spurred shared learning. They provided opportunities for members to grasp new concepts, expand their horizons, and uncover the Power Platform tools' untapped potential. This learning ripple effect will continue to shape our growth. Empowerment: Solutions empowered community members. They validated their knowledge, boosted their confidence, and highlighted their contributions. Each solution shared was a step towards personal and communal empowerment. We are proud and thankful as we conclude the Summer of Solutions Challenge. The challenge showed the potential of teamwork, the benefit of knowledge-sharing, and the resilience of our Power Platform community. The solutions offered by each member are more than just answers; they are the expression of our shared commitment to innovation, growth, and progress!   Drum roll, Please... And now, without further ado, it's time to announce the winners who have risen above the rest in the Summer of Solutions Challenge!   These are the top community users and Super Users who have not only earned recognition but have become beacons of inspiration for us all.   Power Apps Community:  Community User Winner: @SpongYe Super User Winner: Pending Acceptance Power Automate Community:  Community User Winner: @trice602 Super User Winner: @Expiscornovus  Power Virtual Agents Community: Community User Winner: Pending AcceptanceSuper User: Pending Acceptance Power Pages Community: Community User Winner: @OOlashyn Super User Winner: @ChristianAbata   We are also pleased to announced two additional tickets that we are awarding to the Overall Top Solution providers in the following communities:    Power Apps: @LaurensM   Power Automate: @ManishSolanki    Thank you for making this challenge a resounding success. Your participation has reaffirmed the strength of our community and the boundless potential that lies within each of us. Let's keep the spirit of collaboration alive as we continue on this incredible journey in Power Platform together.Winners, we will see you in Vegas! Every other amazing solutions superstar, we will see you in the Community!Congratulations, everyone!

September Featured User Group Leader

   Ayonija Shatakshi, a seasoned senior consultant at Improving, Ohio, is a passionate advocate for M365, SharePoint, Power Platform, and Azure, recognizing how they synergize to deliver top-notch solutions. Recently, we asked Ayonija to share her journey as a user group leader, shedding light on her motivations and the benefits she's reaped from her community involvement.      Ayonija embarked on her role as a user group leader in December 2022, driven by a desire to explore how the community leveraged various Power Platform components. When she couldn't find a suitable local group, she decided to create one herself! Speaking about the impact of the community on her professional and personal growth, Ayonija says, "It's fascinating to witness how everyone navigates the world of Power Platform, dealing with license constraints and keeping up with new features. There's so much to learn from their experiences.    Her favorite aspect of being a user group leader is the opportunity to network and engage in face-to-face discussions with fellow enthusiasts, fostering deeper connections within the community. Offering advice to budding user group leaders, Ayonija emphasized the importance of communication and consistency, two pillars that sustain any successful community initiative.      When asked why she encourages others to become user group leaders, Ayonija said, "Being part of a user group is one of the best ways to connect with experienced professionals in the same field and glean knowledge from them. If there isn't a local group, consider starting one; you'll soon find like-minded individuals."      Her highlight from the past year as a user group leader was witnessing consistent growth within the group, a testament to the thriving community she has nurtured. Advocating for user group participation, Ayonija stated, "It's the fastest route to learning from the community, gaining insights, and staying updated on industry trends."   Check out her group: Cleveland Power Platform User Group

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