cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Palani
Frequent Visitor

Need sample code for context.webAPI.updateRecord method (ComponentFramework) in my PCF

Hello expert community,

 

I am trying to use context.webAPI.updateRecord method (ComponentFramework) in my PCF for updating some of the lookup fields and also to close an Opportunity as Won or Lost. 

 

I tried several ways but I am not able to make the updateRecord method work.  Its giving me error message related to datatype of the attributes.  I am looking for some sample code for the following.

1.  Using context.webAPI.updateRecord method for updating lookup fields.

2.  Using context.webAPI.updateRecord method for closing an Opportunity as Won or Lost.  Note, I don't see the execute method in context.WebAPI, so am wondering if updateRecord must be used for closing a record

 

I tried to pass the EntityReference object returned by the context.utils.lookupObjects method to update a lookup field (parentaccountid) of Opportunity using the updateRecord method as shown below but that did not work.  I tried using _parentaccountid_value, but the error message I received said we cannot update some properties directly in CRM

 

 

 

let oppForUpdate = { "parentaccountid": selectedItem[0] }; //didn't work
//let oppForUpdate = { "_parentaccountid_value": selectedItem[0].id }; //didn't work

this._context.webAPI.updateRecord("opportunity", recordGuid, recordToUpdate).then
			(
				function (updatedRecord: ComponentFramework.EntityReference) {
					console.log("UpdateOpportunityRecord:  Record updated successfully.  ");
				},
				function (errorResponse: any) {
					console.log("UpdateOpportunityRecord:  Record update failed.  " + errorResponse.toString());
				}
			);

 

 

 

For updating an Opportunity as Won or Lost I am trying to pass below data to the updateRecord method again.

 

 

 

    let oppCloseAsWon = { "statecode": 1 };

    let oppCloseAsLost = { "statecode": 2, "statuscode": 4 };

 

 

 

Regards,

Palani K.B.

2 ACCEPTED SOLUTIONS

Accepted Solutions
v-xida-msft
Community Support
Community Support

Hi @Palani ,

Do you want to use the context.webAPI.updateRecord method to update LookUp field and Option Set type column in your Opportunity Entity?

 

Based on the formula that you mentioned, I think there is something wrong with it. Firstly, in order to get the guid value (accountid) of the selected account from the LookUp dialog launched using context.utils.lookupObjects method, please use the following formula:

selectedItem[0].id.guid

Note: The id attribute under the EntityReference object is also a Object value rather than a guid string value. Please check the following article for more details:

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/reference/entityreference

 

For updating LookUp field (parentaccountid):

Actually, the LookUp field is a object value in underlying data structure of CDS Entity, it should contain the following two attributes:

logicalname
id

So you need to declare your oppForUpdate variable as below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.guid
                                         }
                   }

or

let oppForUpdate = { 
                      "parentaccountid@odata.bind": "/accounts(" + selectedItem[0].id.guid + ")"
                   }

Please check the following article for more details:

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webap...

So the whole formula should like below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.guid
                                         }
                   };
this._context.webAPI.updateRecord("opportunity", recordGuid, oppForUpdate).then
			(
				function (updatedRecord: ComponentFramework.EntityReference) {
					console.log("UpdateOpportunityRecord:  Record updated successfully.  ");
				},
				function (errorResponse: any) {
					console.log("UpdateOpportunityRecord:  Record update failed.  " + errorResponse.toString());
				}
			);

Note: I assume that the parentaccountid LookUp field reference values from the Account Entity.

 

For updating Option Set field in your Opportunity Entity, I think your variable declare is correct. Combined with above feature, you should declare the oppForUpdate object as below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.guid
                                         },
                       "statecode": 2,
                       "statuscode": 4
                   }

The whole formula should like below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.guid
                                         },
                       "statecode": 2,
                       "statuscode": 4
                   };
this._context.webAPI.updateRecord("opportunity", recordGuid, oppForUpdate).then
			(
				function (updatedRecord: ComponentFramework.EntityReference) {
					console.log("UpdateOpportunityRecord:  Record updated successfully.  ");
				},
				function (errorResponse: any) {
					console.log("UpdateOpportunityRecord:  Record update failed.  " + errorResponse.toString());
				}
			);

or

let oppForUpdate = { 
                       "parentaccountid@odata.bind": "/accounts(" + selectedItem[0].id.guid + ")",
                       "statecode": 2,
                       "statuscode": 4
                   };
this._context.webAPI.updateRecord("opportunity", recordGuid, oppForUpdate).then
			(
				function (updatedRecord: ComponentFramework.EntityReference) {
					console.log("UpdateOpportunityRecord:  Record updated successfully.  ");
				},
				function (errorResponse: any) {
					console.log("UpdateOpportunityRecord:  Record update failed.  " + errorResponse.toString());
				}
			);

Please check the following blog for more details:

https://somacrm.wordpress.com/2018/05/15/dynamics-365-xrm-webapi-update-record-example/

 

Please take a try with above solution, then check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

Hi @Palani , 

The execute Method for the webAPI is not documented, so it's not supported for now. Calling special requests is similar to calling custom actions, because you need there also the execute method.

The execute method is there and works, even if in the typescript definition is not provided. So you could use it...

 

A supported approach is to implement your own XmlHttpRequest  to call the webAPI.

Maybe this thread will help you (there is even an answer for "WinOpportunity" there): https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/How-to-call-custom-actions-using-PCF/m-p/...

Hope it helps.

 

Kind regards,

Diana

Kind regards,
Diana
----------
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

View solution in original post

7 REPLIES 7
v-xida-msft
Community Support
Community Support

Hi @Palani ,

Do you want to use the context.webAPI.updateRecord method to update LookUp field and Option Set type column in your Opportunity Entity?

 

Based on the formula that you mentioned, I think there is something wrong with it. Firstly, in order to get the guid value (accountid) of the selected account from the LookUp dialog launched using context.utils.lookupObjects method, please use the following formula:

selectedItem[0].id.guid

Note: The id attribute under the EntityReference object is also a Object value rather than a guid string value. Please check the following article for more details:

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/reference/entityreference

 

For updating LookUp field (parentaccountid):

Actually, the LookUp field is a object value in underlying data structure of CDS Entity, it should contain the following two attributes:

logicalname
id

So you need to declare your oppForUpdate variable as below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.guid
                                         }
                   }

or

let oppForUpdate = { 
                      "parentaccountid@odata.bind": "/accounts(" + selectedItem[0].id.guid + ")"
                   }

Please check the following article for more details:

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webap...

So the whole formula should like below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.guid
                                         }
                   };
this._context.webAPI.updateRecord("opportunity", recordGuid, oppForUpdate).then
			(
				function (updatedRecord: ComponentFramework.EntityReference) {
					console.log("UpdateOpportunityRecord:  Record updated successfully.  ");
				},
				function (errorResponse: any) {
					console.log("UpdateOpportunityRecord:  Record update failed.  " + errorResponse.toString());
				}
			);

Note: I assume that the parentaccountid LookUp field reference values from the Account Entity.

 

For updating Option Set field in your Opportunity Entity, I think your variable declare is correct. Combined with above feature, you should declare the oppForUpdate object as below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.guid
                                         },
                       "statecode": 2,
                       "statuscode": 4
                   }

The whole formula should like below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.guid
                                         },
                       "statecode": 2,
                       "statuscode": 4
                   };
this._context.webAPI.updateRecord("opportunity", recordGuid, oppForUpdate).then
			(
				function (updatedRecord: ComponentFramework.EntityReference) {
					console.log("UpdateOpportunityRecord:  Record updated successfully.  ");
				},
				function (errorResponse: any) {
					console.log("UpdateOpportunityRecord:  Record update failed.  " + errorResponse.toString());
				}
			);

or

let oppForUpdate = { 
                       "parentaccountid@odata.bind": "/accounts(" + selectedItem[0].id.guid + ")",
                       "statecode": 2,
                       "statuscode": 4
                   };
this._context.webAPI.updateRecord("opportunity", recordGuid, oppForUpdate).then
			(
				function (updatedRecord: ComponentFramework.EntityReference) {
					console.log("UpdateOpportunityRecord:  Record updated successfully.  ");
				},
				function (errorResponse: any) {
					console.log("UpdateOpportunityRecord:  Record update failed.  " + errorResponse.toString());
				}
			);

Please check the following blog for more details:

https://somacrm.wordpress.com/2018/05/15/dynamics-365-xrm-webapi-update-record-example/

 

Please take a try with above solution, then check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-xida-msft 

 

Hi Kris Dai,

 

Thank you so much for your suggestion and really sorry I could not let you know my findings sooner.

 

Here below are my findings.

 

1.  The object selectedItem[0].id does not have a property called guid.  It contains the GUID of the record in curly braces and I had to remove the curly braces in order to use the GUID for updating the record using WebAPI (let selectedItemGUIDstring = selectedItem[0].id.replace("{""").replace("}""");)

 

2.  For updating Lookup fields using webAPI.updateRecord, the below format worked for me.

                    let valueToUpdatestring = "/accounts(" + selectedItemGUID + ")";
                    let oppForUpdate = { "parentaccountid@odata.bind": valueToUpdate };
 
Here below is the code I am using now to update the lookup field based on the response from the
context.utils.lookupObjects method

 

	private LookUpDialog(entityName: string, fieldName: string): void {
		var lookUpOptions: any = {
			entityTypes: [entityName]
		};
		var lookUpPromise: any = this._context.utils.lookupObjects(lookUpOptions);
		lookUpPromise.then((selectedItem: any) => {	
				if (selectedItem && selectedItem[0]) {
					let selectedItemGUID: string = selectedItem[0].id.replace("{", "").replace("}", "");
					let valueToUpdate: string = "/accounts(" + selectedItemGUID + ")";
					let oppForUpdate = { "parentaccountid@odata.bind": valueToUpdate };
					this.UpdateOpportunityRecord(this._props.recordDetails?.recordId as string, oppForUpdate);
				}
			},
			(error: any) => {
				// Error handling code here
			}
		);
	}

 

 

I am still having issues updating the statecode and statuscode of the record using the below format.  Kindly help me there if I am doing something wrong.  

 

Here below is the object I am using 

image.png

 

Here's the error I am receiving and the error message is generic.

image.png

 

Also, I could not find the execute method as part of the WebAPI object yet. Please confirm if that is not yet supported.

 

Kindly share an example for setting DateTime fields too.

 

Your help is much appreciated.

 

Thanks and Regards,

Palani K.B.  

Hi @Palani ,

Firstly, I agree with your modification on my formula almost. Do you mean that the 

updateRecord

function is not available under the webAPI Client API on your side?

 

I have made a test on my side, and don't have the issue that you mentioned. The screenshot as below:

4.JPG

 

Before you could use the webAPI functionality in your PCF Project, you must have enabled the webAPI uses-feature in your ControlManifest.Input.xml file as below:

5.JPG

<feature-usage>
      <uses-feature name="WebAPI" required="true" />
</feature-usage>

More details about the uses-feature element in PCF, please check the following article:

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/f...

 

Best regards, 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-xida-msft 

 

Hi Kris,

 

I am able to see the updateRecord method under the WebAPI client api.  However, I am not able to see the Execute method which we use to execute various other types of requests in CDS.

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webap...

 

Note, I have already included the feature-usage and uses-feature property in my ControlManifest.Input.xml file and I am able to successfully use retrieveRecord, retrieveMultipleRecords and updateRecord method too, but I am not able to use this updateRecord method to close an Opportunity record as Won or Lost.  When I try to set the statecode and statuscode as shown in the screenshot below, I am getting an error message.

 

image.png

 

image.png

 

Can you please share an example of how to close an Opportunity as Won or Lost using updateRecord method. 

 

Regards,

Palani K.B.

Hi @Palani ,

You mean the formula I provided above could update a LookUp field properly, but not a Option Set type column?

 

Please consider initialize the object variable in your .ts file as below:

let oppForUpdate = { 
                      "parentaccountid": {
                                            "logicalname": "account",
                                            "id": selectedItem[0].id.replace("{", "").replace("}", "")
                                         },
                       "statecode": {
                                      "value": 0,
                                      "label": "Active"
                                    },
                       "statuscode": {
                                         "value": 1,
                                         "label": "Active"
                                     }
                   }

The Option Set type column is essentially a Entity Reference Object, which contains the following two attributes:

2.JPG

 

Please consider take a try with above solution, then check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @Palani , 

The execute Method for the webAPI is not documented, so it's not supported for now. Calling special requests is similar to calling custom actions, because you need there also the execute method.

The execute method is there and works, even if in the typescript definition is not provided. So you could use it...

 

A supported approach is to implement your own XmlHttpRequest  to call the webAPI.

Maybe this thread will help you (there is even an answer for "WinOpportunity" there): https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/How-to-call-custom-actions-using-PCF/m-p/...

Hope it helps.

 

Kind regards,

Diana

Kind regards,
Diana
----------
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

@DianaBirkelbach Thanks a lot for your suggestion.  This is what I was looking for.  This would help me move forward now.  I will accept your answer as a solution.

 

@v-xida-msft Hi Kris, I tried your latest suggestion for updating the optionset value as mentioned by you but it did not work again and threw an error as shown below.  However, your suggestion for the lookup field did help me and thanks a lot for that. 

 

image.png

 

Error Message: 

"An error occurred while validating input parameters: Microsoft.OData.ODataException: An unexpected 'StartObject' node was found for property named 'statecode' when reading from the JSON reader. A 'PrimitiveValue' node was expected.
   at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadPrimitiveValue(Boolean insideJsonObjectValue, IEdmPrimitiveTypeReference expectedValueTypeReference, Boolean validateNullValue, String propertyName)
   at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadNonEntityValueImplementation(String payloadTypeName, IEdmTypeReference expectedTypeReference, PropertyAndAnnotationCollector propertyAndAnnotationCollector, CollectionWithoutExpectedTypeValidator collectionValidator, Boolean validateNullValue, Boolean isTopLevelPropertyValue, Boolean insideResourceValue, String propertyName, Nullable`1 isDynamicProperty)
   at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadEntryDataProperty(IODataJsonLightReaderResourceState resourceState, IEdmProperty edmProperty, String propertyTypeName)
   at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadPropertyWithValue(IODataJsonLightReaderResourceState resourceState, String propertyName, Boolean isDeltaResourceSet)
   at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.<>c__DisplayClass9_0.<ReadResourceContent>b__0(PropertyParsingResult propertyParsingResult, String propertyName)
   at Microsoft.OData.JsonLight.ODataJsonLightDeserializer.ProcessProperty(PropertyAndAnnotationCollector propertyAndAnnotationCollector, Func`2 readPropertyAnnotationValue, Action`2 handleProperty)
   at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadResourceContent(IODataJsonLightReaderResourceState resourceState)
   at Microsoft.OData.JsonLight.ODataJsonLightReader.StartReadingResource()
   at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadResourceSetItemStart(PropertyAndAnnotationCollector propertyAndAnnotationCollector, SelectedPropertiesNode selectedProperties)
   at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadAtStartImplementationSynchronously(PropertyAndAnnotationCollector propertyAndAnnotationCollector)
   at Microsoft.OData.ODataReaderCore.ReadImplementation()
   at Microsoft.OData.ODataReaderCore.InterceptException[T](Func`1 action)
   at System.Web.OData.Formatter.Deserialization.ODataReaderExtensions.ReadResourceOrResourceSet(ODataReader reader)
   at System.Web.OData.Formatter.Deserialization.ODataResourceDeserializer.Read(ODataMessageReader messageReader, Type type, ODataDeserializerContext readContext)
   at System.Web.OData.Formatter.ODataMediaTypeFormatter.ReadFromStream(Type type, Stream readStream, HttpContent content, IFormatterLogger formatterLogger)"

Regards,
Palani K.B.

Helpful resources

Announcements

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   Heartholme     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   Dorrinda   G1124   Gabibalaban   Manan-Malhotra   jcfDaniel   WarrenBelz   Waegemma      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. 

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. 

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 

Users online (2,285)