InfoPath Dev

We are testing migration from SharePoint 2007 to 2013.

Following is the error we get when we try to open InfoPath forms with rules existing under @finishedLoading attribute.

Form template: https://spsite2013/sites/acc/PO/forms/template.xsn?OpenIn=PreferClient&NoRedirect=true&XsnLocation=/sites/acc/PO/forms/template.xsn
The following DataObject either cannot be created or cannot be initialized: QdabraRules
InfoPath cannot add the following object to the DataObjects collection: QdabraRules
QdabraRules could not be added to the DataObjects collection.

The form definition (.xsf) file contains the following error:
Illegal value http://spsite2007/QdabraRules/@finishedLoading for match attribute of domEventHandler declaration
Expected value type: end-of-string

Actual value: :
http-->:<--//spsite2007/QdabraRules/@finishedLoading

This error doesn't come up on forms with no rules under @finishedLoading attribute.

Can someone throw any insights into fixing this please?

Thanks!

I've not seen this. Can you please go to one of the migrated libraries, and under the settings > advanced settings, edit the template & save the template locally, then email the template file to support AT qdabra DOT com or attach it under the Options tab in this thread? If you email the template, please include a link to this thread.

Thanks!

 Thanks Hilary! I have emailed the template.

Thanks for emailing me the templates. Here's what I did -

I extracted the source files from both templates.

In the original manifest.xsf, I see this:

 <xsf:domEventHandlers>
  <xsf:domEventHandler match="/QdabraRules/@finishedLoading" dataObject="QdabraRules">
   <xsf:ruleSetAction ruleSet="ruleSet_1"></xsf:ruleSetAction>
  </xsf:domEventHandler>
 </xsf:domEventHandlers>

In the one from your site upgrade, I see this:

 <xsf:domEventHandlers>
  <xsf:domEventHandler match="http://myms/QdabraRules/@finishedLoading" dataObject="QdabraRules">
   <xsf:ruleSetAction ruleSet="ruleSet_1"></xsf:ruleSetAction>
  </xsf:domEventHandler>
 </xsf:domEventHandlers>

Do you see how something changed the domEventHandler match attribute? I have no idea what might be doing that. Is it possible to just plan on republishing these templates after your upgrade?

Thanks Hilary. We are using a third party tool to migrate from 2007 to 2013 on a new farm. That seemed to have touched and modified some sections within the manifest.xsf files. The error seemed to have gone after manually fixing the migrated manifest.xsf file and republishing it. Though we have a post-migration fix, we are hoping for a fix with the migration tool itself. Thanks again for looking into it.