Skip to main content

Async Plugins vs. Power Automate Flows

1 comment

SP Error: A Web Part you attempted to change is either invalid or has been removed by another user.

Today I tried to get a custom Sharepoint web part to work. It was no fun because I had a pretty simple (once you figured it out) and tedious error.

I added my custom web part on a standard SharePoint web part page and tried to edit the web part properties. I tried to just click on OK, Apply or Cancel I always got the following annoying message:
A Web Part you attempted to change is either invalid or has been removed by another user.
After spending a couple of hours, even with an experienced collegue, I finally found an interesting article:
http://williamvanstrien.blogspot.com/2010/01/alluserswebpart-and-spwebapplicationapp.html
William pointed out that it is a really bad thing to set the ID of a webpart control:
"...When you add a control within an .aspx file, Visual Studio automatically add a default 'ID' property to the control. For the default WebPart however this is not needed, the property is actually set when creating a publishing page off this PageLayout. But the mere presence of it in the default part results in SharePoint detecting a concurrent update..."

Hence I removed the ID property of my web part and everything was good!


Removing the ID was the very simple trick to this issue.

Thank you Microsoft for providing us developers/users so meaningful error messages.
Labels:

Comments

  1. UnknownNovember 8, 2016 at 9:47 PM

    In my case, we were out of disk space in SQL.
    http://www.sharepointindepth.com/a-web-part-you-attempted-to-change-is-either-invalid-or-has-been-removed-by-another-user/

    ReplyDelete
  2. UnknownNovember 8, 2016 at 9:48 PM

    In my case, we were out of disk space in SQL.
    http://www.sharepointindepth.com/a-web-part-you-attempted-to-change-is-either-invalid-or-has-been-removed-by-another-user/

    ReplyDelete

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...
16 comments
Read more

Async Plugins vs. Power Automate Flows

Choosing Your Automation Tool Choosing the right tool for automation and business logic in the Power Platform and Dynamics 365 is crucial for building scalable, maintainable, and performant solutions. Both asynchronous plugins and Power Automate flows can execute logic in the background, but they are designed for different scenarios and user profiles. This interactive guide provides a comparative overview to help you determine the most suitable option for your specific requirements. At-a-Glance Comparison This chart provides a visual summary of the relative strengths of each tool across key decision factors. Hover over the points for more details. Interactive Criterion Explorer Sel...
1 comment
Read more

CRM 2013: Translation import error: The value passed for ConditionOperator.In is empty

This week a very evil error drove me nuts. In CRM 2013 I tried to import a translation file into an organization. It always ended up with this error message: The value passed for ConditionOperator.In is empty I was like what in the world does this message mean. If an old school approach in splitting up the file into serveral smaller Import files I finally figured out that the following lines in the "Localized Labels" sheet caused this trouble: RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.HomepageGrid.Group0.Control0.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.HomepageGrid.Group0.Control0.ToolTip.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.SubGrid.Group0.Control0.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.SubGrid.Group0.Control0.ToolTip.LocLabel To resolve t...
Post a Comment
Read more