I am using a SharePoint integrated form and have collected the selected record in a collection.
I am then modifying this record inside the collection via form and Patch functions.
At the end I wanted to patch the changes back to the datasource via:
- Patch(SharePointList,myCollection)
But I am countinuously getting the error: {VersionNumber}: The specified column is read-only and can't be modified...
I have tried to drop the version number via DropColumns function but then I get error for another field and another field and another field...
Please kindly support what is the issue... I think this should supposed to work since the columns in source and Collection are the same.. (i have a high number of columns though, around 70...)
Solved! Go to Solution.
Hi @Student2 :
Could you show me the data structure of myCollection?
Firstly,let me explain why you encounted this problem.
The point is {VersionNumber} is a standard read-only field in the sharepoint list. There are many such fields, such as:ID,Modified,Created……
Secondly,I suggest you filter out the required fields to update.
For example:
Patch(SharePointList,ShowColumns(myCollection,"Column1","Column2","Column3"))
Or
ForAll(
mycollection
Patch(SharePointList,Defaults(SharePointList),{Column1:Column1,Column2:Column2})
)
Best Regards,
Bof
Hi @Student2 :
Could you show me the data structure of myCollection?
Firstly,let me explain why you encounted this problem.
The point is {VersionNumber} is a standard read-only field in the sharepoint list. There are many such fields, such as:ID,Modified,Created……
Secondly,I suggest you filter out the required fields to update.
For example:
Patch(SharePointList,ShowColumns(myCollection,"Column1","Column2","Column3"))
Or
ForAll(
mycollection
Patch(SharePointList,Defaults(SharePointList),{Column1:Column1,Column2:Column2})
)
Best Regards,
Bof
@v-bofeng-msft is this still the only working solution in 2022? If all required fields need to be mentioned in the formula it's hard to maintain it.
This is a huge problem! Why isn't there a way to drop all read-only columns?
How about this, Microsoft: if read-only columns always cause errors when patching data to SharePoint, wouldn't it be logical to always remove read-only columns from patch requests? Why should the user have to specify every single modifiable column with ShowColumns() or every single read-only column with DropColumns()????
Isn't it obvious that the patch request should automatically drop all non-modifiable columns? What would be the harm in that? Don't give me an error! Just patch my data and make it work.
This is such a major annoyance with developing canvas apps that talk to SharePoint, it just seems like the solution is glaringly obvious. Or how about this, TELL ME WHICH COLUMN IS READ-ONLY!!!!! The error message "Network error when using Patch function: The specified column is read-only and can't be modified." is frustratingly incomplete. Seriously, just tell me which columns I have to drop and I'll drop them. As it stands, I've gone down the entire list of auto-suggested columns and can't seem to find the remaining read-only columns. So, my next option would be to forget using DropColumns() and switch to ShowColumns() but that's an even worse solution because of how many columns are in this list. I should not have to explicitly specify every single modifiable column or every single read-only column in order to patch some data. This is ridiculous!
Signed in just to say YES! Agreed. WHICH COLUMN!!! Such a dumb error. Suddenly this morning all my app versions goes back days are giving this error, when the app worked fine yesterday. I have no idea what's happening or how I can fix it.
Try adding the following code to the "on Error" field on the App (Select App from the Tree view on the left, then On Error from the properties on the right.)
Notify(
Concat(Errors(YourTableorList), Column&": "&Message),
NotificationType.Error
)
It then told me what the offending column was next time the error occurred.
Hope this helps someone else in the future.
Hello ccuginotti,
I'd tried something similar, but yours worked much better, and I got a column name! Thanks!
Only problem is... it's telling me every single column name in the list (see attachment)
These are not read only columns, they're columns I created myself as "Person" columns. I actually re-created the whole list an hour ago in case it was a list issue. There are 9 "person" columns, and 1 "lookup" column. This is to ensure I'm under the 12 maximum advanced fields (adding created by, modified by, gets to 12).
Edit: Deleted all Person/Lookup except one, and it still errored. Then I realised it's happening to another list and another part of the app not updated in weeks. So I wonder if I've hit some kind of limit/restriction, or if there's a database issue in our region... logged with support.
Update: after I finished work, Microsoft Support got back to me and logged a defect in PowerApps that was later fixed. Surely I was'nt the only one experiencing this yesterday...
Details:
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