Skip to main content

Power Automate: SharePoint Copy file action fails on file names with a plus (+) sign

Post a 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

Regarding SPFieldMultiLineText (Add HTML/URL content to a field) programmatically

I recently tried so set some HTML content in a SharePoint list column of type SPFieldMultiLineText. My first approach was this piece of code: SPFieldMultiLineText field = item.Fields.GetFieldByInternalName( "Associated Documents" ) as SPFieldMultiLineText; StringBuilder docList = new StringBuilder(); docList.Append( " " ); foreach (DataRow docRow in addDocs) { DataRow[] parent = dr.Table.DataSet.Tables[0].Select( "DOK_ID=" + docRow[ "DOK_MGD_ID" ].ToString()); if (parent != null && parent.Length > 0) { docList.AppendFormat( " {1} " , parent[0][ "FilePath" ].ToString(), parent[0][ "Title" ].ToString()); } } if (docList.Length > 0) { // remove trailing tag docList.Remove(docList.Length-5, 5); } docList.Append( " " ); string newValue = docList.ToString(); item[field.Title] = newValue; What this code does is to get all associated documents to the main document and to add these docu
1 comment
Read more

CRM 2013: Condition for attribute 'template.templatetypecode': null is not a valid value for an attribute. Use 'Null' or 'NotNull' conditions instead.

Lately I was fighting with an issue that on some CRM instances the default email templates view in the Templates section of CRM 2013 did not show up and only showed me this error message: Condition for attribute 'template.templatetypecode': null is not a valid value for an attribute. Use 'Null' or 'NotNull' conditions instead. After searching for a long time I found the simple bug. Throught migration from 4.0 to CRM 2013 over CRM 2011 and changing customizations it seemed that CRM got messed up or was not able to handle the changes very well. The issue here was to go to the views section of the Email Templates entity and to make sure there is only ONE default public view. If there are two you will get strange system behavior. I fixed this problem through updating the isdefault property of the second unwanted default view in the SavedQueryBase data table. The id of this view  you can retrieve by openen the view and by copying it out from the URL. Én voi
1 comment
Read more