cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
PowerApps11
Helper V
Helper V

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

Power Platform Connections - Episode 6 | March 23, 2023

Episode Six of Power Platform Connections sees David Warner and Hugo Bernier talk to talk to Business Applications MVP Shane Young, alongside the latest news, product updates, and community blogs.    Use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show!      Show schedule in this episode:  0:00 Cold Open 00:24 Show Intro 01:02 Shane Young Interview 22:00 Blogs & Articles 22:20 Integrate FullCalendar.io with Power Pages 23:50 Text Data 25:15 Zero to Hero Power Apps Saga 25:44 Parent Hub Association 26:33 Using Custom Values for OneNote Power Automate References​ 28:04 ​Dynamics Power Israel 28:44 Create Beautiful Canvas Apps in Dataverse for Teams ​ 30:36 Outro & Bloopers  Check out the blogs and articles featured in this week’s episode:   https://francomusso.com/integrate-fullcalendar-io-with-power-pages-from-json-basics-to-advanced-outp... @crmbizcoach https://yerawizardcat.com/text/ @YerAWizardCat www.fromzerotoheroes.com/mentorship ​ @thevictordantas https://www.expiscornovus.com/2023/03/16/parent-hub-association/ ​ @Expiscornovus https://lindsaytshelton.com/2023/03/15/the-painful-process-of-custom-values-for-onenote-power-automa... @lshelton_Tech https://never-stop-learning.de/create-beautiful-canvas-apps-in-dataverse-for-teams/ @MMe2K    Action requested: Feel free to provide feedback on how we can make our community more inclusive and diverse.  This episode premiered live on our YouTube at 12pm PST on Thursday 23rd March 2023.  Video series available at Power Platform Community YouTube channel.    Upcoming events:  Business Applications Launch – April 4th – Free and Virtual! M365 Conference - May 1-5th - Las Vegas Power Apps Developers Summit – May 19-20th - London European Power Platform conference – Jun. 20-22nd - Dublin Microsoft Power Platform Conference – Oct. 3-5th - Las Vegas  Join our Communities:  Power Apps Community Power Automate Community Power Virtual Agents Community Power Pages Community  If you’d like to hear from a specific community member in an upcoming recording and/or have specific questions for the Power Platform Connections team, please let us know. We will do our best to address all your requests or questions. 

Announcing | Super Users - 2023 Season 1

Super Users – 2023 Season 1    We are excited to kick off the Power Users Super User Program for 2023 - Season 1.  The Power Platform Super Users have done an amazing job in keeping the Power Platform communities helpful, accurate and responsive. We would like to send these amazing folks a big THANK YOU for their efforts.      Super User Season 1 | Contributions July 1, 2022 – December 31, 2022  Super User Season 2 | Contributions January 1, 2023 – June 30, 2023    Curious what a Super User is? Super Users are especially active community members who are eager to help others with their community questions. There are 2 Super User seasons in a year, and we monitor the community for new potential Super Users at the end of each season. Super Users are recognized in the community with both a rank name and icon next to their username, and a seasonal badge on their profile.    Power Apps  Power Automate  Power Virtual Agents  Power Pages  Pstork1*  Pstork1*  Pstork1*  OliverRodrigues  BCBuizer  Expiscornovus*  Expiscornovus*  ragavanrajan  AhmedSalih  grantjenkins  renatoromao    Mira_Ghaly*  Mira_Ghaly*      Sundeep_Malik*  Sundeep_Malik*      SudeepGhatakNZ*  SudeepGhatakNZ*      StretchFredrik*  StretchFredrik*      365-Assist*  365-Assist*      cha_cha  ekarim2020      timl  Hardesh15      iAm_ManCat  annajhaveri      SebS  Rhiassuring      LaurensM  abm      TheRobRush  Ankesh_49      WiZey  lbendlin      Nogueira1306  Kaif_Siddique      victorcp  RobElliott      dpoggemann  srduval      SBax  CFernandes      Roverandom  schwibach      Akser  CraigStewart      PowerRanger  MichaelAnnis      subsguts  David_MA      EricRegnier  edgonzales      zmansuri  GeorgiosG      ChrisPiasecki  ryule      AmDev  fchopo      phipps0218  tom_riha      theapurva  takolota     Akash17  momlo     BCLS776  Shuvam-rpa     rampprakash  ScottShearer     Rusk  ChristianAbata     cchannon  Koen5     a33ik        AaronKnox        Matren        Alex_10        Jeff_Thorpe        poweractivate        Ramole        DianaBirkelbach        DavidZoon        AJ_Z        PriyankaGeethik        BrianS        StalinPonnusamy        HamidBee        CNT        Anonymous_Hippo        Anchov        KeithAtherton        alaabitar        Tolu_Victor        KRider        sperry1625        IPC_ahaas      zuurg    rubin_boer   cwebb365      If an * is at the end of a user's name this means they are a Multi Super User, in more than one community. Please note this is not the final list, as we are pending a few acceptances.  Once they are received the list will be updated. 

Microsoft Power Platform Conference | Registration Open | Oct. 3-5 2023

We are so excited to see you for the Microsoft Power Platform Conference in Las Vegas October 3-5 2023! But first, let's take a look back at some fun moments and the best community in tech from MPPC 2022 in Orlando, Florida.   Featuring guest speakers such as Charles Lamanna, Heather Cook, Julie Strauss, Nirav Shah, Ryan Cunningham, Sangya Singh, Stephen Siciliano, Hugo Bernier and many more.   Register today: https://www.powerplatformconf.com/   

Check out the new Power Platform Communities Front Door Experience!

We are excited to share the ‘Power Platform Communities Front Door’ experience with you!   Front Door brings together content from all the Power Platform communities into a single place for our community members, customers and low-code, no-code enthusiasts to learn, share and engage with peers, advocates, community program managers and our product team members. There are a host of features and new capabilities now available on Power Platform Communities Front Door to make content more discoverable for all power product community users which includes ForumsUser GroupsEventsCommunity highlightsCommunity by numbersLinks to all communities Users can see top discussions from across all the Power Platform communities and easily navigate to the latest or trending posts for further interaction. Additionally, they can filter to individual products as well.       Users can filter and browse the user group events from all power platform products with feature parity to existing community user group experience and added filtering capabilities.     Users can now explore user groups on the Power Platform Front Door landing page with capability to view all products in Power Platform.    Explore Power Platform Communities Front Door today. Visit Power Platform Community Front door to easily navigate to the different product communities, view a roll up of user groups, events and forums.

Welcome to the Power Apps Community

Welcome! Congratulations on joining the Microsoft Power Apps community! You are now a part of a vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun! Now that you are a member, you can enjoy the following resources:   The Microsoft Power Apps Community Forums If you are looking for support with any part of Microsoft Power Apps, our forums are the place to go. They are titled "Get Help with Microsoft Power Apps " and there you will find thousands of technical professionals with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Apps community forums! Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered!   Microsoft Power Apps IdeasDo you have an idea to improve the Microsoft Power Apps experience, or a feature request for future product updates? Then the "Power Apps Ideas" section is where you can contribute your suggestions and vote for ideas posted by other community members. We constantly look to the most voted Ideas when planning updates, so your suggestions and votes will always make a difference.   Community Blog & NewsOver the years, more than 600 Power Apps Community Blog Articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on building Power Apps. On the Power Apps Community Blog, read the latest Power Apps related posts from our community blog authors around the world. Let us know if you would like to become an author and contribute your own writing — everything Power Apps related is welcome!   Power Apps Samples, Learning and Videos GalleriesOur galleries have a little bit of everything to do with Power Apps. Our galleries are great for finding inspiration for your next app or component. You can view, comment and kudo the apps and component gallery to see what others have created! Or share Power Apps that you have created with other Power Apps enthusiasts. Along with all of that awesome content, there is the Power Apps Community Video & MBAS gallery where you can watch tutorials and demos by Microsoft staff, partners, and community gurus in our community video gallery.   Again, we are excited to welcome you to the Microsoft Power Apps community family! Whether you are brand new to the world of process automation or you are a seasoned Power Apps veteran. Our goal is to shape the community to be your ‘go to’ for support, networking, education, inspiration and encouragement as we enjoy this adventure together!   Let us know in the Community Feedback if you have any questions or comments about your community experience.To learn more about the community and your account be sure to visit our Community Support Area boards to learn more! We look forward to seeing you in the Power Apps Community!The Power Apps Team

Microsoft Power Platform | March 2023 Newsletter

Welcome to our March 2023 Newsletter, where we'll be highlighting the great work of our members within our Biz Apps communities, alongside the latest news, video releases, and upcoming events. If you're new to the community, be sure to subscribe to the News & Announcements and stay up to date with the latest news from our ever-growing membership network who find real "Power in the Community".    LATEST NEWS Power Platform Connections Check out Episode Five of Power Platform Connections, as David Warner II and Hugo Bernier chat with #PowerAutomate Vice President, Stephen Siciliano, alongside reviewing out the great work of Vesa Juvonen, Waldek Mastykarz, Maximilian Müller, Kristine Kolodziejski, Danish Naglekar, Cat Schneider, Victor Dantas, and many more.   Use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show!   Did you miss an episode?  Catch up now in the Community Connections Galleries Power Apps, Power Automate, Power Virtual Agents, Power Pages     Power Platform leading a new era of AI-generated low-code development.   **HOT OFF THE PRESS** Fantastic piece here by Charles Lamanna on how we're reinventing software development with Copilot in Power Platform to help you can build apps, flows, and bots with just a simple description! Click here to see the Product Blog         Copilot for Power Apps - Power CAT Live To follow on from Charles' blog, check out #PowerCATLive as Phil Topness gives Clay Wesener Wesner a tour of the capabilities of Copilot in Power Apps.       UPCOMING EVENTS   Modern Workplace Conference Check out the Power Platform and Microsoft 365 Modern Workplace Conference that returns face-to-face at the Espace St Martin in Paris on 27-28th March. The #MWCP23 will feature a wide range of expert speakers, including Nadia Yahiaoui, Amanda Sterner, Pierre-Henri, Chirag Patel, Chris Hoard, Edyta Gorzoń, Erika Beaumier, Estelle Auberix, Femke Cornelissen, Frank POIREAU, Gaëlle Moreau, Gilles Pommier, Ilya Fainberg, Julie Ecolivet, Mai-Lynn Lien, Marijn Somers, Merethe Stave, Nikki Chapple, Patrick Guimonet, Penda Sow, Pieter Op De Beéck, Rémi Riche, Robin Doudoux, Stéphanie Delcroix, Yves Habersaat and many more.  Click here to find out more and register today!     Business Applications Launch 2023 Join us on Tuesday 4th April 2023 for an in-depth look into the latest updates across Microsoft Power Platform and Microsoft Dynamics 365 that are helping businesses overcome their biggest challenges today. Find out about new features, capabilities, and best practices for connecting data to deliver exceptional customer experiences, collaborating and creating using AI-powered capabilities, driving productivity with automation, and building future growth with today’s leading technology. Click Here to Register Today!       Power Platform Conference 2023 We are so excited to see you for the Microsoft Power Platform Conference in Las Vegas October 3-5th, 2023! But first, let's take a look below at some fun moments from MPPC 2022 in Orlando Florida. 2023 sees guest speakers such as Charles Lamanna, Heather Cook, Julie Strauss, Nirav Shah, Ryan Cunningham, Sangya Singh, and many more taking part, so why not click the link below to register for the #PowerPlatformConf today! Vegas, baby! Click Here to Register Today!      COMMUNITY HIGHLIGHTS Check out our top Super and Community Users reaching new levels!  These hardworking members are posting, answering questions, kudos, and providing top solutions in their communities.   Power Apps:  Super Users:  @WarrenBelz  |  @iAm_ManCat  Community Users: @LaurensM | @Rusk | @RJM07    Power Automate:   Super Users: @abm  | @Expiscornovus | @RobElliott  Community Users:  @grantjenkins | @Chriddle    Power Virtual Agents:   Super Users: @Expiscornovus | @Pstork1  Community Users: @MisterBates | @Jupyter123 | Kunal K   Power Pages: Super Users:  @OliverRodriguesOliverRodrigues | @Mira_Ghaly  Community Users: @FubarFubar | @ianwukianwuk  LATEST PRODUCT BLOG ARTICLES  Power Apps Community Blog  Power Automate Community Blog  Power Virtual Agents Community Blog  Power Pages Community Blog  Check out 'Using the Community' for more helpful tips and information:  Power Apps, Power Automate, Power Virtual Agents, Power Pages 

Top Solution Authors
Top Kudoed Authors
Users online (1,784)