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

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Users online (2,253)