I've a SharePoint 2013 list modified with InfoPath. Everything was working fine until today, I had to do few modifications. While publishing the changes I'm getting the below error.
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
<detail><errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">
List does not exist.
The page you selected contains a list that does not exist. It may have been deleted by another user.
</errorstring><errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/">0x82000006</errorcode></detail>
Please let me know if there is a way to fix it.
I recently ran into the exact same error message. In my case, the InfoPath Form was created with InfoPath 2010 and migrated to Sharepoint 2013. Editing with InfoPath 2013 yields the error message above. Editing with Infopath 2010 I can edit the form without any issue.
Perhaps its because you have a lookup field in your list, and during import process the link to lookup list is broken
Related
I have configure SharePoint site in my local system, While I am going to create forms I am getting error
SharePoint Designer deprecated please check these two articles:
https://microsoft365.today/microsoft-365/powerapps/sharepoint-designer-feature-deprecation/
https://learn.microsoft.com/en-us/sharepoint/what-s-new/what-s-deprecated-or-removed-from-sharepoint-...
You could try to 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
Reference:
Could not save the List Changes to Server in Sharepoint 2013
Here are another similar thread you could have a look:
"could not save the list changes to the server" in designer
How to create an error pop up in Sharepoint desginer 2013?
Is there a way where, I can set a user message if a condition check fails in Sharepoint desginer 2013?
If you want to add error popup in a list form using SharePoint designer 2013, we can open the form page and find the "PlaceHolderMain", then add some JavaScript code in the below.
If you want to make the error popup works in all page, we can add the code into in master page using SharePoint designer.
If I misunderstand your requirement, I suggest you provide more information for further research.
We're migrating a very complicated Infopath template from Sharepoint 2013 to Sharepoint Online. This template requires domain permissions and a lot of custom code, so a browser-enabled form is not possible.
In Sharepoint 2013, we share the template file (.xsn) which people can click on and it will open in InfoPath Form Filler, where they can do their work. Nobody actually submits the form, because the data is kept on a database.
In Sharepoint Online, the .xsn file will open in Designer view. This is an issue because the users are non-technical people and we don't want them to have to click through to preview or accidentally change something.
We've published the form in a Form Library, but when someone tries to create a new Form, it'll open correctly in InfoPath Filler Form, but give an XML error.
"The form contains XML that cannot be parsed: An invalid character was found in text content. Line 1, Position 5 MSCF"
When I check out the underlying template, I can Edit the Template, which again opens up InfoPath Designer with no issues.
I've also exported out the XML for the template and spot no XML errors and can open it in InfoPath designer, so I'm at a loss about how to debug the XML error.
So, we can go either route to resolve the issue:
1) Continue putting the template file on the Sharepoint folders and having users click on it and fill in data, but it must open in Filler Form, not Designer.
2) Fix the issue with the XML Form error (how do I go about even debugging this?) I've exported out the template as a .XML file, but can not spot any XML errors.
Thanks.
Your other option is to get rid of infopath and use a custom form using javascript in classic UI mode OR develop an SPFX webpart that achieve the same thing as your infopath ?
I have a custom field type that was built for SharePoint 2010 that I have installed on SharePoint 2013 Foundation. The wsp installed perfectly and I get all the same functionality.
The one problem I am having is how the information is displayed in the list view. I am inheriting an SPFieldLookup and am not doing anything to override how this is displayed in the list view.
On SharePoint 2010 it renders perfectly as a hyperlink to the item which opens the standard pop out window on click etc. On SharePoint 2013 Foundation however the html doesn't render properly at all- it is almost as though it is displaying as plain text.
SharePoint 2010:
SharePoint 2013 Foundation:
My question is how can I get the lookup value to render properly on SharePoint 2013?
The same version of the wsp in installed on both machines.
Unsure as to whether this was simply a browser or client side issue I added a standard lookup field to the list and it renders fine!
I had the same issue with my codeplex project which is based on Lookup field. I added a link to dummy JS file and overrode the JSLink property of the field class. I have blogged about it here: http://sharepointnadeem.blogspot.in/2013/12/sharepoint-2013-upgrade-sharepoint-2010.html
In SP 2013 by default field rendering is done on client side. Concept of JSLink has been introduced if you want to change the look and feel of field.
However by ClientRender=False in new form url you can force it to server render mode.
So after an afternoon of head scratching it turns out that this is not a deployment issue. It probably didn't even warrant a question but for anyone who has the same problem as me...
If you edit the page and modify the listview settings you will see that there is a new setting called "Server Render".
I guess this ultimately gives you more control but in may case it prevented my fields from rendering as expected- turning this on meant my custom fields we once again displayed 'normally'.
I'm working in a sharepoint 2010 workflow with an infopath form. When I check in my dev machine, the workflow and form are working fine. But when I deploy it to the production server I get an error in the second step when I'm trying to submit the InfoPath form, the error says "The file '[url_of_the_file]' is checked out for editing by '[user]'". I have all the versioning settings off for that library.
It seems that when I modify the item in the workflow, it somehow is getting checked out and then the user that has the second step gets this error.
Any ideas?
Thanks in advance.
Juan Escobar.
There is an Action called "Checkin Item" in SharePoint Workflow, you can try to insert the action before you make any changes to your current item.