Tool: InfoPath 2010
A client was customizing a list view with InfoPath 2010 when the view hit a snag. The view would no longer publish to the SharePoint list. There were a few changes to the list column definitions and the InfoPath command to Refresh the SharePoint Schema was being diligently used to keep everything in sync.
Each time there were changes to sync, a refresh of the SharePoint Schema was performed. Immediately after, a Quick Publish followed where an error dialog was presented with the following …
“The SOAP response indicates that an error occurred on the server”.
“Server was unable to process request. —> Object reference not set to an
instance of an object.”
The following attempts provided for a successful resolution.
- Refresh List Schema
Along the top Command Bar of the UI, include the icon to Refresh SharePoint Schema
– Refresh the Schema
– Republish to the List
- Design Checker
Let InfoPath inform you of the warnings and errors that it is thinking about
– Select the menu option of File > Design Checker
– Double-Click each warning/error to be taken to the view column
– Inspect and replace the suspect columns with a fresh copy from the list
The Design Checker pointed to a column whose definition in the source list had changed. The column in the form had become Unbound so I simply deleted the existing and replaced it with the column from the source list.
Saved the Form > Republished > Complete
Never edit the original view of a list!
Instead, perform the following steps so that you have a fall back plan …
- always create a new view
- copy (Ctrl+A) and paste (Ctrl+V) the content from the original view
- modify the new view as needed
- then assign the custom view to the appropriate list function (create, edit, list)
Once InfoPath is opened and you start messing with the custom view
- column description changes are not transferred to the form; you need to manually revise the descriptions of each custom view from then on
- column definitions, if changed from Single Line to Multiple Line, etc… may not transfer to the form; you may need to refresh the Schema and then manually remove and re-add the affected columns of each custom view
[run File > Design Checker early and often to verify changes]
How has Sharepoint affected you?