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

DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

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.
DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

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

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders     Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Tuesday Tip | How to Provide Feedback

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   We are always looking to improve your experience on our community platform, and your feedback is invaluable to us. Whether it's a suggestion for a new feature, an idea to enhance the platform, or a concern you'd like to address, we want to hear from you!   How to Share Your Feedback: Each of our communities has its own Feedback forum where the Community Managers can assist you directly in.  ●  Power Apps  ● Power Automate   ● Power Pages   ● Copilot Studio   We also have many articles on community account FAQs, or how to navigate the community, which can be found below.   Community Accounts & Registration:  https://powerusers.microsoft.com/t5/Community-Accounts-Registration/tkb-p/pa_community_accounts_regi...   Using the Community: https://powerusers.microsoft.com/t5/Using-the-Community/tkb-p/pa_using_the_community   Our Commitment to You: We are committed to creating a collaborative and supportive environment. All feedback is reviewed by our community managers, and we strive to implement changes that will benefit all members.   Thank you for being a part of our community. Your contributions help us grow and improve together!

Copilot Cookbook Challenge | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.

May 2024 Community Newsletter

It's time for the May Community Newsletter, where we highlight the latest news, product releases, upcoming events, and the amazing work of our outstanding Community members.   If you're new to the Community, please make sure to follow the latest News & Announcements and check out the Community on LinkedIn as well! It's the best way to stay up-to-date with all the news from across Microsoft Power Platform and beyond.        COMMUNITY HIGHLIGHTS Check out the most active community members of the last month! These hardworking members are posting regularly, answering questions, kudos, and providing top solutions in their communities. We are so thankful for each of you--keep up the great work! If you hope to see your name here next month, follow these awesome community members to see what they do!   Power AppsPower AutomateCopilot StudioPower PagesWarrenBelzcreativeopinionExpiscornovusFubarAmikNived_NambiarPstork1OliverRodriguesmmbr1606ManishSolankiMattJimisonragavanrajantimlSudeepGhatakNZrenatoromaoLucas001iAm_ManCatAlexEncodianfernandosilvaOOlashynJmanriqueriosChriddle  BCBuizerExpiscornovus  a33ikBCBuizer  SebSDavid_MA  dpoggermannPstork1     LATEST NEWS   We saw a whole host of amazing announcements at this year's #MSBuild, so we thought we'd share with you a bite sized breakdown of the big news via blogs from Charles Lamanna, Sangya Singh, Ryan Cunningham, Kim Manis, Nirav Shah, Omar Aftab, and ✊🏾Justin Graham :   New ways of development with copilots and Microsoft Power PlatformRevolutionize the way you work with Automation and AIPower Apps is making it easier for developers to build with Microsoft Copilot and each otherCopilot in Microsoft Fabric is now generally available in Power BIUnlock new levels of productivity with Microsoft Dataverse and Microsoft Copilot StudioMicrosoft Copilot Studio: Building copilots with agent capabilitiesMicrosoft Power Pages is bringing the new standard in secure, AI-powered capabilities   If you'd like to relive some of the highlights from Microsoft Build 2024, click the image below to watch a great selection of on-demand Keynotes and sessions!         WorkLab Podcast with Charles Lamanna   Check out the latest episode of the WorkLab podcast with CVP of Business Apps and Platforms at Microsoft, Charles Lamanna, as he explains the ever-expanding evolution of Copilot, and how AI is offering new opportunities for business leaders. Grab yourself a coffee and click the image below to take a listen.       Event Recap: European Collaboration and Cloud Summits 2024   Click the image below to read a great recap by Mark Kashman about the recent European Collaboration Summit and European Cloud Summit held in Germany during May 2024. Great work everybody!       UPCOMING EVENTS European Power Platform Conference - SOLD OUT! Congrats to everyone who managed to grab a ticket for the now SOLD OUT European Power Platform Conference, which takes place in beautiful Brussels, Belgium, on 11-13th June. With a great keynote planned from Ryan Cunningham and Sangya Singh, plus expert sessions from the likes of Aaron Rendell, Amira Beldjilali, Andrew Bibby, Angeliki Patsiavou, Ben den Blanken, Cathrine Bruvold, Charles Sexton, Chloé Moreau, Chris Huntingford, Claire Edgson, Damien Bird, Emma-Claire Shaw, Gilles Pommier, Guro Faller, Henry Jammes, Hugo Bernier, Ilya Fainberg, Karen Maes, Lindsay Shelton, Mats Necker, Negar Shahbaz, Nick Doelman, Paulien Buskens, Sara Lagerquist, Tricia Sinclair, Ulrikke Akerbæk, and many more, it looks like the E in #EPPC24 stands for Epic!   Click the image below for a full run down of the exciting sessions planned, and remember, you'll need to move quickly for tickets to next year's event!       AI Community Conference - New York - Friday 21st June Check out the AI Community Conference, which takes place at the Microsoft Corporate building on Friday 21st June at 11 Times Square in New York City. Here, you'll have the opportunity to explore the latest trends and breakthroughs in AI technology alongside fellow enthusiasts and experts, with speakers on the day including Arik Kalininsky, Sherry Xu, Xinran Ma, Jared Matfess, Mihail Mateev, Andrei Khaidarov, Ruven Gotz, Nick Brattoli, Amit Vasu, and more. So, whether you're a seasoned professional or just beginning your journey into AI, click the image below to find out more about this exciting NYC event.       TechCon365 & Power Platform Conference - D.C. - August 12-16th ** EARLY BIRD TICKETS END MAY 31ST! ** Today's the perfect time to grab those early bird tickets for the D.C. TechCon365 & PWRCON Conference at the Walter E Washington Center on August 12-16th! Featuring the likes of Tamara Bredemus, Sunny Eltepu, Lindsay Shelton, Brian Alderman, Daniel Glenn, Julie Turner, Jim Novak, Laura Rogers, Microsoft MVP, John White, Jason Himmelstein, Luc Labelle, Emily Mancini, MVP, UXMC, Fabian Williams, Emma Wiehe, Amarender Peddamalku, and many more, this is the perfect event for those that want to gain invaluable insights from industry experts. Click the image below to grab your tickets today!         Power Platform Community Conference - Sept. 18-20th 2024 Check out some of the sessions already planned for the Power Platform Community Conference in Las Vegas this September. Holding all the aces we have Kristine Kolodziejski, Lisa Crosbie, Daniel Christian, Dian Taylor, Scott Durow🌈, David Yack, Michael O. and Aiden Kaskela, who will be joining the #MicrosoftCommunity for a series of high-stakes sessions! Click the image below to find out more as we go ALL-IN at #PPCC24!       For more events, click the image below to visit the Community Days website.                                            

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!      

Users online (5,068)