InfoPath Dev

Hi, We're testing migrating content from SharePoint 2007 to 2010. We have a mixture of Office 2010 and 2007 users, but all InfoPath dev is done in 2007. Everything looks great in the new environment except for the InfoPath forms. I believe that I can change data connections and save paths, then publish existing forms to the 2010 site without error (I haven't tried it yet), but with the one big app I have that uses Qrules, nothing I try has been successful. So, perhaps I'm breaking it by trying to fix it. These are not browser-enabled forms. (I would like to go that direction, but we're not quite ready for that.) Is there a gentle way to migrate Qrules-injected forms from SharePoint 2007 to 2010? We're using the database attach upgrade method. Thanks for your help, Nancy

Hi Nancy,

What type of errors are you getting?

I would think that as long as the forms are injected correctly (2007 vs 2010, browser vs client) and the data connections (for example, if using SubmitToSharePointList) are updated for the new server, then qRules should continue working.

Let us know what type of errors/issues you saw and we'll help you out. Thanks.

I changed the data connections, but then I realized I needed to change the mapping files (4 of them), so I redid them to change the hard-coded server path to the SharePoint list. I guess I could have just edited the xml files, but there are so many of them. My original mapping files are: ExecMappingGFMC ExecMappingGFMCLLC ExecMappingGFMCLLCProjects ExecMappingGFProjects QdabraRules.xml But now, after many, many edits to this form, which works perfectly in SP 2007, there are, in addition to the above: ExecMappingGFMC 2 ExecMappingGFMC1. ExecMappingGFMC2. ExecMappingGFMCLLC1. ExecMappingGFMCLLC2. ExecMappingGFMCLLCProjects1. ExecMappingGFMCLLCProjects2. ExecMappingGFMCLLCProjects3. ExecMappingGFMCProjects1. ExecMappingGFMCProjects2. Which ones would I change? All of them? The error I'm getting is vague, possibly because I'm using preview to test? It says: Errors occurred submitting to list: The operation failed because an unexpected error occurred. (Result Code: 0x80020005) However, the success box is checked. I'm using v3.1. I'll publish it to the test server and see if that makes a difference. In the meantime, do you have any suggestions? Thanks, n.

 InfoPath keeps a history of the mapping files, but you'll just need to edit the highest numbered one.

You'll notice that the mapping files have a URL to the library but they also have a GUID (it's a key SharePoint generates for each list, a series of characters and numbers) for the list. This also needs to be updated.

The unexpected error might be due to the mismatch between the URL on the new server and the GUID in the old server.

Let us know what you find and whether you need assistance. Thanks.

 

I did notice that after I posted. The list GUIDs is the same on the old server and new one. I'll let you know what else I find.

 Ok, let us know what you discover. Thanks.