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

Check Out the February 2024 Dynamics 365 Newsletter

Some of our most active Power Platform Community members are also active in our D365 Community. This month, we are excited to share the latest news from the D365 Community with you.   Our Dynamics365 Community has updated yet again! Since launching in June of 2023, the new Community has seen consistent updates and exciting new ways to feature and celebrate its members. In the latest edition of the Dynamics365 Community newsletter, you can see the new Leaderboard feature! This feature showcases which Community members have earned the most points over the previous month, enabling them to see how they are doing with their engagement--and their progress toward Super User status. Visit the leaderboard for yourself: https://aka.ms/d365clb     Read the whole newsletter featuring the new leaderboard as well as the D365 Monthly Community Member spotlight, FastTrack Tech Talks, upcoming events, and more. February 2024 Dynamics 365 Community Newsletter

Celebrating a New Season of Super Users with Charles Lamanna, CVP Microsoft Business Applications

February 8 was the kickoff to the 2024 Season One Super User program for Power Platform Communities, and we are thrilled to welcome back so many returning Super Users--as well as so many brand new Super Users who started their journey last fall. Our Community Super Users are the true heroes, answering questions, providing solutions, filtering spam, and so much more. The impact they make on the Communities each day is significant, and we wanted to do something special to welcome them at our first kickoff meeting of the year.   Charles Lamanna, Microsoft CVP of Business Applications, has stressed frequently how valuable our Community is to the growth and potential of Power Platform, and we are honored to share this message from him to our 2024 Season One Super Users--as well as anyone who might be interested in joining this elite group of Community members.     If you want to know more about Super Users, check out these posts for more information today:    Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

February 2024 User Group Update: Welcoming New Groups and Highlighting Upcoming Events

It's a new month and a brand-new year, which means another opportunity to celebrate our amazing User Groups!Each month, we highlight the new User Groups that have joined the community. It's been a busy season for new groups, because we are thrilled to welcome 15 New User Groups! Take a look at the list below, shared by the different community categories. If your group is listed here, give this post a kudo so we can celebrate with you!   We love our User Groups and the difference they make in the lives of our Community! Thank you to all the new User Groups, new User Group leaders--we look forward to hearing about your successes and the impact you will leave!   In addition to our monthly New User Group spotlight, it's a great time to share some of the latest events happening in our User Group community! Take a look at the list below to find one that fits your schedule and need! There's a great combination of in-person and virtual events to choose from. It's a great time of year to connect and engage with User Groups both locally and online. Please Welcome Our NEW User Groups   Power Platform: Heathcare Power Platform User Group Power Platform Connect Hub Power Platform Usergroup Denmark Mexico Norte- Power Platform User Group Pune Power User Group Sudbury Power Platform User GroupMicrosoft User Group GhanaMPPBLR - Microsoft Power Platform Bengaluru User Group Power Apps:   Myrtle Beach Power Platform User GroupAnanseTechWB PowerApps Copilot Studio: Pathfinders Power Platform Community Dynamics365: Cairo, Egypt MSD 365 Business Central/NAV/F&O User GruopMS Dynamics 365 Business Central LatamCincinnati OH D365 F&O User Group February User Group Events February 2024 Cleveland Power Platform User GroupPortallunsj - Februar 2024Indiana D365/AX February User Group MeetingQ1 2024 KC Power Platform and Dynamics 365 CRM Users Group 

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

January 2024 Community Newsletter

Welcome to our January Newsletter, where we highlight the latest news, product releases, upcoming events, and the amazing work of our outstanding Community members. If you're new to the Community, please make sure to follow the latest News & Announcements in each Community and check out the Community on LinkedIn as well! It's the best way to stay up-to-date in 2024 with all the news from across Microsoft Power Platform and beyond.      COMMUNITY HIGHLIGHTS Check out the most active community members of the last month! These hardworking members are posting regularly, answering questions, giving (and receiving!) kudos, and consistently providing top solutions in their communities. We are so thankful for each of you--keep up the great work! If you hope to see your name here next month, make it your New Year's Resolution to be more active in the community in 2024.   Power AppsPower AutomateCopilot StudioPower PagesWarrenBelzWarrenBelzPstork1saudali_25LaurensMPstork1stephenrobertLucas001AARON_ClbendincpaytonSurendran_RANBNived_NambiarMariamPaulachanNikhil2JmanriqueriosANBJupyter123rodger-stmmbr1606Agniusstevesmith27mandelaPhineastrice602AnnaMoyalanOOlashynBCLS776grantjenkinsExpiscornovusJcookSpongYeAARON_CManishSolankiapangelesPstork1ManishSolankiSanju1Fubar   LATEST NEWS Power Platform 2024 Release Wave Highlights This month saw the 2024 Release Wave 1 plans for Microsoft Power Platform and Microsoft Dynamics 365- a compilation of new capabilities planned for release between April and September 2024. Click here to read Corporate Vice President Maureen (Mo) Osborne's detailed breakdown of the upcoming capabilities, and click the image below to check out some of the Power Platform 2024 Release Wave 1 highlights.     "What's New" Power Platform Shorts Series This month we also launched our brand-new 'Power Shorts' series on YouTube - a selection of super sweet snapshots to keep you in the loop with all the latest trends from across the Power Platform and beyond. Click the image below to check out the entire playlist so far, and don't forget to subscribe to our YouTube channel for all the latest updates.   Super User In Training (S.U.I.T) It was great to see the Power Platform Community officially kick off Season One of their Super User in Training (SUIT) program this month! Their first meeting saw an amazing turnout of over 300 enthusiastic participants who started their dynamic journey toward becoming Super Users. Huge thanks to Manas Maheshwari, Eric Archer, Heather Hernandez, and Duane Montague for a fantastic kick-off. The first meeting also saw seasoned Super User, Drew Poggemann, share invaluable insights on navigating the #MicrosoftCommunity with finesse. Many thanks to Drew for setting the stage and emphasizing the importance of active engagement and the art of providing thoughtful community solutions. If you want to learn more about the features and benefits of gaining Super User status, click the image below to find out more, and watch this space for more info about Season Two and how you can SUIT UP in the community!     UPCOMING EVENTS Microsoft 365 Community Day - Miami - February 1-2, 2024 It's not long now until the Microsoft 365 Community Day Miami, which will be taking place at the Wolfson Campus at Miami Dade College on 1-2 Feb. 2024. This free event is all about unlocking the full potential of Power Platform, Microsoft 365, and AI, so whether you’re a tech enthusiast, a business owner, or just curious about the latest Microsoft advancements, #M365Miami is for you.   The event is completely free and there will sessions in both English and Spanish to celebrate the vibrant and diverse make-up of our amazing community. Click the image below to join this amazing Community Day in Miami and become a part of our incredible network of learners and innovators!     Microsoft Fabric - Las Vegas - March 26-28, 2024 Exciting times ahead for the inaugural #MicrosoftFabric Community Conference on March 26-28 at the MGM Grand in Las Vegas. And if you book now, you can save $100 off registration! The Microsoft Fabric Conference will cover all the latest in analytics, AI, databases, and governance across 150+ sessions.   There will be a special Community Lounge onsite, interactive learning labs, plus you'll be able to 'Ask the Experts' all your questions to get help from data, analytics, and AI specialists, including community members and the Fabric Customer Advisory Team. Just add the code MSCUST when registering for a $100 discount today. Click the image below to find out more about the ultimate learning event for Microsoft Fabric!     Microsoft 365 Conference - Orlando - April 30 - May 2, 2024 Have you added The Microsoft 365 Conference to your community calendar yet? It happens this April 30th - May 2nd in Orlando, Florida. The 2024 Microsoft 365 Conference is one of the world’s largest gatherings of Microsoft engineers and community, with a strong focus on Power Platform, SharePoint, Azure, and the transition to an AI-powered modern workplace.   Click the image link below to find out more and be prepared to be enlightened, educated, and inspired at #M365Conf24!   LATEST COMMUNITY BLOG ARTICLES Power Apps Community Blog Power Automate Community Blog Copilot Studio Community Blog Power Pages Community Blog Check out 'Using the Community' for more helpful tips and information: Power Apps, Power Automate, Copilot Studio, Power Pages  

Did You Attend the Microsoft Power Platform Conference in 2022 or 2023? Claim Your Badge Today!

If you were one of the thousands of people who joined us at the first #MPPC Microsoft Power Platform Conference in 2022 in Orlando--or attended the second-annual conference in Las Vegas in 2023--we are excited to honor you with a special community badge! Show your support for #MPPC Microsoft Power Platform Conference this year by claiming your badge!         Just follow this link to claim your badge for attending #MPPC in 2022 and/or 2023: MPPCBadgeRequest    Want to earn your badge for 2024? Just keep watching our News & Announcements for the latest updates on #MPPC24.

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