Hi everbody,
I cam creating a custom connector to connect with a partner solution of Microsoft Dynamics Business Central.
Business Central provie some API features which is the base for the custom connector.
Scenario:
- Types of Request: GET, POST and PATCH
- GET and POST Request are working fine on every part: Postman, CustomConnector Test Area and PowerApps
- PATCH Request is only working with POSTMAN and Custom Connector Test Area. On PowerApps I always get the information, that another user has already changed the record.
Detail information on Patch:
- To send the PATCH Request I need to send the information / node "etag" with the request
- The "etag" information is placed within the header and the key "If-Match"
Screenshot of the parameter setup for "If-Match" on CustomConnector
Currently I assume that this setup may cause this error because of Type = string.
Has anybody else worked with API, PATCH Request and "If-Match" yet?
Solved! Go to Solution.
in base, all version of BC work in general.
The message you get is purely from a wrong inputted etag.
check in your get comment if the @odata.etag is Type:string Format: ""
Same for the if-Match parameter Type: string Format: ""
Also do you patch the same entity as where the get is from?
Etags are page related, so if you get from a different page then to which you patch you also may experience the error
Hi jiwanovski,
You are almost there.
The etag is a dynamic feature of a record, it says which "version" of the record you want to modify.
if the current version of bc and your version are a match than the modification is allowed.
so what you want to do is:
-http (get) the latest E-tag of the record you want to modify
- http(Patch) the just received e-tag in the if-Match.
This way BC accepts your change because your change is based on the latest "version"
Hi @Anonymous
thank you for your quick response.
Aktually I do this already, but I still get the message, that some User has changed the dataset before.
What I am doing:
- First I get a set of records of a table with a GetRequest
- This is assigned as Item for a gallery
- In gallery I have some controls to modify single fields and an icon to save
- With the OnSelect of the icon I try to do the PATCH. Here I just reference to the ThisItem.'@odata.etag' to give the etag information....
But I still get the error message "Another user has changed the record"....
Any idea what I should test?
Which version of BC have you tested (which client build?)
in base, all version of BC work in general.
The message you get is purely from a wrong inputted etag.
check in your get comment if the @odata.etag is Type:string Format: ""
Same for the if-Match parameter Type: string Format: ""
Also do you patch the same entity as where the get is from?
Etags are page related, so if you get from a different page then to which you patch you also may experience the error
Hi @jiwanovski ,
Have you taken a try to remove the "W/" prefix from the ETag value (default value) you set for the If-Match header in your Patch request?
Please consider take a try to remove the "W/" prefix from the ETag value (default value) you set for the If-Match header in your Patch request, then try your custom connector again, check if the issue is solved.
In addition, the ETag value of the "If-Match" header is required to provide a string of ASCII characters rather than a HTML text. Please check the following article for more details:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag
Please consider set Format property to Blank as below:
Please take a try with above solution, then check if the issue is solved.
Best regards,
Hi everbody,
I agree that this should be a format problem of the etag value.
For the GET and the PATCH request I use the same API Page. So I have believed that I just can take the value from GET response.
I also modified the etag parameter to String blank (GET and PATCH) again. This was the value by default (I just changed this in case of testing purpose).
I also tried to eleminate the removing the prefix "w/" value and set this to header with "If-Match" or just do put the "@odata.etag" direct into the Body.... Nothing helped...
What I wonder if there is anything on the value of the GET response itself wrong?
This is how it looks like in Postman
"@odata.etag": "W/\"JzQ0O1c1a1JkaDE3RW80QUxsR3FkVm0rNGZOUDJSekNSN0VXdkI0RlpyN0NWNXM9MTswMDsn\""
I also tried to just remove the "\" in this string...
Any other ideas?
Hi everybody,
@Anonymous and I just had a short call on that and he was already right before.
When I tried to send the PATCH Request, I hadn't the correct etag value in place.
How it is not working:
(1) Get a list of records (including a etag value) with somethink like: https://yourURL.com/BC130/api/V1/API/beta/companies/:companyId/APIEntity?$filter=ID eq dbeb2692-1fa6-490d-9f54-147a3e422a5e
(2) Add this to a gallery
(3) Add Buttion to do the PATCH Request
(4) In OnSelect calling PATCH Request like: https://yourURL.com/BC130/api/V1/API/beta/companies/:companyId/APIEntity/:entityID
If you do it like this way, you will get always that another user has changed the record.
Before you do Step (4) you have to do a single API Request like: https://yourURL.com/BC130/api/V1/API/beta/companies/:companyId/APIEntity/:entityID
So even both GET Request are based on the same Page in BC I first have to do the GET statement for the single record and take the etag value from there. Then it is running.
So many thanks to @Anonymous!!!!
The solved answer should get to you!
Hi @jiwanovski
How did you create your body of the patch call.
When patching we only need to send updated field data like
{"itemName": "New Itemname"},
But in a scenario where PowerApp user might change 1 or more out of 10 possible fields, I would like to supply my updated field(s) name and field(s) value(s).
Thanks
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 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
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