I'm working on an internal sharepoint-webpart for my company. Since a few days I've got troubles while inserting webparts und pages.
I'm trying to add the webpart as ever but after selecting it and pressing the add button SharePoint seems to do something but stops with an message like-. "Could not add element because Element is deleted from the cataloge" It's strange cause the WebPart is displayed in the List of custom webparts...
Does somebody have an idea or had a similar problem?
Thanks
Spanky
it took some hours more but now it works. While searching for the problem I saw that the webparts still apear in SharePoint-Catalog after retracting them.
As I now know Sharepoint does not delete the .webpart files while retracting whem..Somehow it does not udpate them either.. I guess this is a specific problem.
But after I had deleted the .webparts file and a new deployment -...it works..
More information here -> Link
Bye Spanky
Related
I am working in Sharepoint Designer 2013 for my Sharepoint in Windows 365. I want to create a custom Form using Sharepoint Designer however when I click create a new form and then save this new form I get an error message:
I tried cleaning out the cache in location c:/Users/user/Appdata/Local/Microsoft/WebsiteCache
Has anyone had this problem and found a solution for it?
Could you follow some advice mentioned below:
Step 1: Create a new list item on your list. If it works, go to step 2. If doesn't, check our list columns (or content types of that list) - specially calculated fields and lookup fields.
Step 2: Create new custom form by SharePoint Designer 2013. If it doesn't work, try to clear SPD cache in location:
c:/Users/[your current user]/Appdata/Local/Microsoft/WebsiteCache
Hope it will help.
If anyone has landed here in 2020 onwards looking for the answer, the reason is that Microsoft have deprecated this feature.
https://techcommunity.microsoft.com/t5/sharepoint/sharepoint-designer-could-not-save-list-changes-to-server/m-p/1352320
I know there are threads out there about making changes to the refinement panel and they have so far been very helpful but now I have a question that I need a bit more assistance with.
I've created a new filter for the refinement panel. That worked very fine.
I can see the filter, when I perform a search.
But when I click on the new filter, all search results disappear and it just says: "We did not find any results for ".
I can see that the url gets my created filter attached:
results.aspx?...&r=filterfield%3D%22True%22
I have created a managed metadata property and added the field to the search results (search core results webpart).
What I'm doing wrong? Why it doesn't work?
Any hints?
Thanks for any help.
I found the reason. I forgot to start a full crawl after creating the managed metadata field.
I can change and save everything but when i open site, which contains Content Query Web Part showin items from my newList, webPart style isnt updated. In fact its using old ItemStyle file (i think so) which i already overwritten a few times. I thought its a common problem with designer WebSiteCache but already tried that and nothing. Im also ofc checkin in a major version and still the same. Funny thing is that everything is displayed properly for everyone else in my office :(
SharePoint By default do setting to cache css and javascript at browser side. So to see changes in your conten Query webpart try Ctr+F5. May be it solve your problem.
We're working with a sharepoint 2007 site that has a number of dataview webparts showing different views of a document repositry. Each time we make even the most minor change (such as changing the chrome settings or adding a class) to the XSLT or webpart settings the DV webpart refuses to render.
Our XSL is vaild, as is the page the GUID is correct for the list and we are at a loss. We've resorted to editing the CAML files deleting and reimporting them which is obviously very slow. Any thoughts/ideas/help would be much appreciated.
I have faced this problem at our place too. Often I have found out that it is because of JS errors. Do you notice any errors on the IE? Did you try refershing the page by doing a CTRL+F5? I hope this helps, coz at times it does for me. I dont know the root cause and never cared to look into since it has happened only a few times.
I have a SharePoint Designer workflow like the following: (just an example)
If ActionId equals 1
Email InfopathForms:Customer Email
Sometime later, it changes itself to the following:
If field equals 1
Email InfopathForms:
Where the field ActionId is lost and the Customer Email is lost too. Also in the email body, all the Lookup fields are also lost...
Has anyone had this problem before...?
This has happened like 6-7 times already... If anyone know a solution to fix it please let me know... much appreciated!!!!!!!!!!!!!!!
And is there some way to backup the workflow...? So I can easily restore it after it resets itself..?
sharepoint designer is not the most useful tool for developing and deploying workflows. I have not experieced this problem. Somthing simliar when two dev's were attacking the same list with sharepoint designer. could this be your problem?
I've noticed similar symptoms when variable names change... Is your InfoPath form changing? Or are the promoted fields changing? If so, I would expect this behavior. Simple fix is to update the variables in the workflow step, and then leave the InfoPath form alone. :D
We have the same issue.
I found that the lookup fieldname in the xoml file is diffrent if you re-link (pick) it.
An example: FieldName="WFOrder_x0020_Type" after re-link it is FieldName="WFOrder_x0020_Type0"
<ns0:LookupActivity ListId="{}{8FC10225-9397-4F5A-88B6-FE4C37A44970}" x:Name="ID645" FieldName="**WFOrder_x0020_Type**" LookupFunction="LookupFriendlyString" __Context="{ActivityBind ROOT,Path=__context}" ListItem="{ActivityBind ROOT,Path=__item}">
I open the xoml file in textpad and edit all the fields by adding the zero into the fieldname. Saved it and my workflow is working again.
Just to clarify, I did modify the InfoPath form and published it, where after my workflow lookup fieldnames got messed up.