InfoPath Dev

Hola,
I recently discovered that the data connections I turned into Connection Files on the SP where my form was published were giving errors to testers.  It seems to be a security issue that my IT department is no help in solving.  If I did NOT turn the connections into Connection Files, the data was returned for these same users.  Because I this, I deleted ALL of the original data connections and then re-created them as basic data connections.

None of the current or previous connections are automatically queried when the form is opened.  All of them are initiated through button clicks. 

During previews of the form, I have discovered that the form seems to be trying to connect to these previous connection files when performing tasks that never had anything to do with initiating a query.  I then get an error and can't move forward with using the form.  Buttons or checkboxes that change form views or trigger section reveals are now causing an error like this:

"The XSL transform for the View XSL failed.
InfoPath
A call to XDocument.GetDOM failed. The DataObject "LD People Directory1" does not exist.
Error occurred during a call to property or method 'GetDOM'."

(Where LD People Directory1 is a previous connection that is now deleted)

Has this occured to anyone else?  I'm at a loss for trouble-shooting this one.

Thank you,

Jen

What is the type of the form (in Compatibility <  Form Options < Info < File on ribbon)

Are you using lookup fields, etc.

Can you include template with your post (in  options tab)?

 Try to Export Source Files of Infopath template locally in Infopath Designer 2010 (on ribbon File > Publish > Export Source Files button), having made a copy, find and deleted parts referencing corresponding to maverick data connections

And don't kill the messenger after that...

 

Thanks Gennady,

Sorry, forgot to include some of that info.  It's a 2010 Filler Form (IT has removed our ability to use Form Services on all of our farms) that is published to 2007 MOSS.  The errors are occurring in preview mode as well as on the site.  By lookup fields, do you mean fields that are utilizing those data connections?  If so, then yes, I do have a number of fields that rely on data connections (dropdown fields and multi-select fields), but all of these connections are triggered by buttons and certain answers to other fields.  I don't have any connections (new or old) that atuomatically connect when the form is opened.

Unfortunately, my form is huge and too big to upload here.  I am actually having to create twin forms and publish to two form libraries in order to split the promoted fields between the two because of the size.

I did export the source files.  I see xsd files with the names of my current data connections, but don't see any of the old ones that are showing up in the errors I'm getting.  Not sure if there's another place to look...

Any other thoughts? 

Thanks for your help!

 manifest.xsf

• Update:
  previously I wrote meaning to search all source files but using manifest.xsf for saving/publishing the changed template

And you should republish template after changes

• Update/Errata:
  I thought you knew, well, under "republish" I did mean saving template under another name locally, republishing implies, for me, previous saving-as Though, it is possible to use template without publishing
  
  As it was described in further replies, open the changed template in Infopath Designer 2010 (by right-clicking on manifest.xsf > Design) and Save As (clicking first File tab on ribbon)
  

In Infopath template form of, for example, "Sharepoint Form List" type (compatibility) I see a lot of additional files per one lookup field.

For example, if I create a list TestList, create an IP form for, export files and then add lookup field to ID of, suppose, ClientList, then in source files I see just because of this, additional files:

•  ClientList.xsd
• ClientList1.xsd
• ClientList2.xsd
• ClientList3.xsd
• ClientList4.xsd
  

as well as additional read-only (Modify... button is active but there is nothing to see except the name of my server) data connecton ClientList to previous Main Data Connection
The Main Data Connection isn't even viewable  (any buttons - Modify..., Remove, Convert to Connection File... are disabled)

The error suggests that the issue is probably in one or more of the form's xsl (view) files.  I'd suggest opening them up in a text editor and searching for LD People Directory1. If you like, you can zip up just the XSLs that contain bad data connection names and upload that ZIP here, and someone can help you figure out how to clean out the problematic stuff. 

Okay, I didn't find the "maverick" connection in the manifest file, but I did find it when I opened the view files that are having the issue.  Any recommendations on how to go about resolving?  I have saved copies of my form just in case this goes awry.

If I open as a txt file, I can edit the data connection name to be the correct name, but am not sure how to resave and if that would even alter anything.

Thanks again for your help with this as I'd prefer not reverting to an older version and redoing much of my work.

Jen

You should be able to open the XSL with a text editor. Make changes and save. Then right click manifest.xsf and select design to try to open in Design mode. If it opens, you can use File --> Save As to pack it back up as an XSN.

Thank you both!  I appear to be back in business!

Fantastic - and you now have yet another little chunk of esoteric InfoPath knowledge at your disposal. :-)

Jen B:

Okay, I didn't find the "maverick" connection in the manifest file, but I did find it when I opened the view files that are having the issue

 

In my 1st reply I wrote "to find", i.e. searching through all source files of template. Any operating systems, Windows is not exception, has built-in functionality of searching for files through all files of a folder (with subfolders).I could not guess that someone is searching by opening and reading files... You should also add this chunk of esoteric knowledge (searching strings in files) to your disposal...

I updated my second answer to make more clear that manifest.xsf I mentioned in context of saving/updating the changed template (in case you made them in source files). This all was of a broad knowledge in Infopath development, frequently mentioned in IP topics

Also, all Infopath template source files are XML files and you would probably prefer opening them in XML-aware text editor. I use for a very long time UEdit32 though probably there are more modern and convenient editors.    

 

Just as an off-topic aside, I like Notepad ++ with the XML Tools plugin when I don't want to bother opening Visual Studio....