Someone asked I review & try to create a simplified template for Dataverse Batch Requests. I think I've built out much of a solution but I'm stuck with some final errors when I send the batch...
I'm basically trying to combine...
This batch create YouTube video: https://www.youtube.com/watch?v=e2zuEBdas0g
@Paulie78's batch delete blog: https://www.tachytelic.net/2021/11/power-automate-bulk-delete-dataverse/
The Dataverse batch documentation: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/execute-batch-operations...
... so we can get some template batch Dataverse set-ups that do not require creating an Azure Application like in Paulie's blog and that also do not require looping to add each record to a variable like Untethered365's YouTube video.
I have created one set-up with the standard batch request and one using change sets. Neither is working but for different reasons.
The standard batch request runs the call successfully but nothing is created in the table. And the response that I get by using base64tostring on the $content doesn't contain much:
Inputs
{
"host": {
"connectionReferenceName": "shared_webcontents",
"operationId": "InvokeHttp"
},
"parameters": {
"request/method": "POST",
"request/url": "/api/data/v9.2/$batch",
"request/headers": {
"OData-MaxVersion": "4.0",
"OData-Version": "4.0",
"If-None-Match": "null",
"Accept": "application/json",
"Content-Type": "multipart/mixed;boundary=batch_18748f86-a56a-43eb-a881-d2faee3586b6"
},
"request/body": "--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637\nContent-Type: application/http\nContent-Transfer-Encoding: binary\n\nPOST /api/data/v9.2/crc5f_test HTTP/1.1\nContent-Type: application/json;type=entry\n\n{\"crc5f_name\":\"ABC0\"}\n\n--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637\nContent-Type: application/http\nContent-Transfer-Encoding: binary\n\nPOST /api/data/v9.2/crc5f_test HTTP/1.1\nContent-Type: application/json;type=entry\n\n{\"crc5f_name\":\"ABC1\"}\n\n--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637\nContent-Type: application/http\nContent-Transfer-Encoding: binary\n\nPOST /api/data/v9.2/crc5f_test HTTP/1.1\nContent-Type: application/json;type=entry\n\n{\"crc5f_name\":\"ABC2\"}\n\n\n--batch_18748f86-a56a-43eb-a881-d2faee3586b6--"
}
}
The change sets gets an error saying "The response is not in a JSON format" but it does return that each request within the batch encountered a 404 error
Inputs
{
"host": {
"connectionReferenceName": "shared_webcontents",
"operationId": "InvokeHttp"
},
"parameters": {
"request/method": "POST",
"request/url": "/api/data/v9.2/$batch",
"request/headers": {
"OData-MaxVersion": "4.0",
"OData-Version": "4.0",
"If-None-Match": "null",
"Accept": "application/json",
"Content-Type": "multipart/mixed;boundary=batch_18748f86-a56a-43eb-a881-d2faee3586b6"
},
"request/body": "--batch_18748f86-a56a-43eb-a881-d2faee3586b6\nContent-Type: multipart/mixed; boundary=changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637\n\n--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637\nContent-Type: application/http\nContent-Transfer-Encoding: binary\nContent-ID: 1\n\nPOST /api/data/v9.2/crc5f_test HTTP/1.1\nContent-Type: application/json;type=entry\n\n{\"crc5f_name\":\"ABC0\"}\n\n--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637\nContent-Type: application/http\nContent-Transfer-Encoding: binary\nContent-ID: 2\n\nPOST /api/data/v9.2/crc5f_test HTTP/1.1\nContent-Type: application/json;type=entry\n\n{\"crc5f_name\":\"ABC1\"}\n\n--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637\nContent-Type: application/http\nContent-Transfer-Encoding: binary\nContent-ID: 3\n\nPOST /api/data/v9.2/crc5f_test HTTP/1.1\nContent-Type: application/json;type=entry\n\n{\"crc5f_name\":\"ABC2\"}\n\n--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637--\n--batch_18748f86-a56a-43eb-a881-d2faee3586b6--"
}
}
Request Body
--batch_18748f86-a56a-43eb-a881-d2faee3586b6
Content-Type: multipart/mixed; boundary=changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637
--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637
Content-Type: application/http
Content-Transfer-Encoding: binary
Content-ID: 1
POST /api/data/v9.2/crc5f_test HTTP/1.1
Content-Type: application/json;type=entry
{"crc5f_name":"ABC0"}
--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637
Content-Type: application/http
Content-Transfer-Encoding: binary
Content-ID: 2
POST /api/data/v9.2/crc5f_test HTTP/1.1
Content-Type: application/json;type=entry
{"crc5f_name":"ABC1"}
--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637
Content-Type: application/http
Content-Transfer-Encoding: binary
Content-ID: 3
POST /api/data/v9.2/crc5f_test HTTP/1.1
Content-Type: application/json;type=entry
{"crc5f_name":"ABC2"}
--changeset_18a52fa6-3edd-4387-9dce-bcaf81f5e637--
--batch_18748f86-a56a-43eb-a881-d2faee3586b6--
Outputs
{
"statusCode": 404,
"headers": {
"Cache-Control": "no-cache",
"x-ms-service-request-id": "2709843e-7f9b-462d-aa9e-c00d5826a0c0,83372510-6d41-4835-acd3-ab1abc9e28a7",
"Set-Cookie": "ARRAffinity=4e3eebc24cdbcaa0e02db39d6138fff60434c67bc35b47bc48e24f6500996011eb29bb4b19df1459d2ea781b605f33064b9fea1f144b525b9d7676625c4ffb5408DC64045EE3B6F3650153111; path=/; secure; HttpOnly,ReqClientId=f322fc9b-a60c-43f2-a367-376253ef08df; expires=Tue, 24-Apr-2074 01:45:11 GMT; path=/; secure; HttpOnly,orgId=c7bcc299-5799-4eef-89f6-4cb7db788477; expires=Tue, 24-Apr-2074 01:45:11 GMT; path=/; secure; HttpOnly,ARRAffinity=4e3eebc24cdbcaa0e02db39d6138fff60434c67bc35b47bc48e24f6500996011eb29bb4b19df1459d2ea781b605f33064b9fea1f144b525b9d7676625c4ffb5408DC64045EE3B6F3650153111; path=/; secure; HttpOnly",
"Strict-Transport-Security": "max-age=31536000; includeSubDomains",
"REQ_ID": "83372510-6d41-4835-acd3-ab1abc9e28a7",
"CRM.ServiceId": "CRMAppPool",
"AuthActivityId": "94e5feef-4a33-46d4-8921-b269458403f7",
"x-ms-dop-hint": "48",
"x-ms-ratelimit-time-remaining-xrm-requests": "1,200.00",
"x-ms-ratelimit-burst-remaining-xrm-requests": "7999",
"mise-correlation-id": "824722d6-343b-40f1-8f4d-f45ab5d737c7",
"OData-Version": "4.0",
"X-Source": "471441764398131032201981022342072422052515127891752058021994198150224828311156221,1672102032264615181561136322221302174321211541661731971841212445922454214216232136125",
"Public": "OPTIONS,GET,HEAD,POST",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "true",
"x-ms-apihub-obo": "false",
"Date": "Wed, 24 Apr 2024 01:45:11 GMT",
"Allow": "OPTIONS,GET,HEAD,POST",
"Content-Length": "900",
"Content-Type": "application/json",
"Expires": "-1"
},
"body": {
"error": {
"code": 404,
"source": "flow-apim-unitedstates-002-westus-01.azure-apim.net",
"clientRequestId": "9d66f57b-f329-471f-97d8-017cbd603f41",
"message": "The response is not in a JSON format.",
"innerError": "--batchresponse_0879d5b9-569d-4cad-b740-dea306b261fd\r\nContent-Type: multipart/mixed; boundary=changesetresponse_6e5882f6-619e-4a87-a8a3-c241e65e65d3\r\n\r\n--changesetresponse_6e5882f6-619e-4a87-a8a3-c241e65e65d3\r\nContent-Type: application/http\r\nContent-Transfer-Encoding: binary\r\nContent-ID: 1\r\n\r\nHTTP/1.1 404 Not Found\r\nContent-Type: application/json; odata.metadata=minimal\r\nOData-Version: 4.0\r\n\r\n{\"error\":{\"code\":\"0x80060888\",\"message\":\"Resource not found for the segment 'crc5f_test'.\"}}\r\n--changesetresponse_6e5882f6-619e-4a87-a8a3-c241e65e65d3--\r\n--batchresponse_0879d5b9-569d-4cad-b740-dea306b261fd--\r\n"
}
}
}
What is wrong with either of my calls and how can I fix either of them?
Solved! Go to Solution.
Figured it out. I was not using the plural logical name for the custom table. Now the changesets version of the flow works.
Hey @takolota I actually made that first video you referenced 🙂 If it continues to cause you issues happy to assist but sounds like you got it resolved.
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!
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 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 SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 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 Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 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 Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
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.
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