-
Your code will likely be an issue when you go from 2007 to 2013, as the object model has some changes. Do you have access to the source code to update it? You should be able to open with InfoPath 2013 in design mode, then try to save as 2013, and deal with the errors that crop up at that time.
-
I really think the issue is that your data types don't match across your lists. If you use a lookup for the column in the reserved materials, then you can filter on the ID (lookups store the ID for the parent list).
-
Search for your Correlation ID from the error. I usually go trigger the error then immediately search the latest log file for the correlation id to make it a bit easier. Sometimes it will be in the prior log file....
-
Check the logs for the correlation id to find out the issue - do you have access to the server?
-
Great job & thanks for posting the solution for others!
-
Not sure what else to suggest - here's an MSDN post that has some links that may help you. https://msdn.microsoft.com/en-us/library/office/aa944896.aspx
-
Oh! Thanks for posting back on this, I hadn't even thought about a missing primary key being the issue.
-
So - that error & correlation ID need to be given to your SharePoint admin so they can check the ULS logs. You may need to disable loopback check on the server to access SharePoint web services from a browser form - this is not always acceptable on a production server and there are other approaches, but get the correlation ID to the SharePoint ...
-
I'd make sure none of the data sources have an issue. Feel free to attach a copy of the form to a reply, under the options tab, if you'd like me to take a look.
-
I'd guess you have a dropdown control that has display unique items selected, and the data connection used for the dropdown is somehow a problem. Can you check your dropdown properties?