InfoPath Dev

Hi,

I'm attempting to modify the CheckIn-Out template part to be used by our organization.  I created the necessary CheckInFile and CheckOutFile UDCX files in a site collection data connection library and modified the manifest to point to the correct path.  When I added the template part to a form, the data connections seem to be recognized without issue, in other words, if I choose Modify for the data connection, the form finds the UDC just fine.  When I run the design checker, I get the following error:  "Invalid form template", with the text "Relative links to Data Connection Libraries located on different SharePoint site collection are not supported." 

This is where I'm confused.  The UDC's are in the same site collection as the published form.  Here's a snippet of the manifest, if that will help:

     <xsf2:webServiceAdapterExtension ref="CheckInFile" trackDataSetChanges="no">
      <xsf2:connectoid connectionLinkType="relative" source="eForms/eForms Data Connections/CheckInFile.udcx" siteCollection="<our local website library>" name="CheckInFile"></xsf2:connectoid>

It's identical to the path of a working UDC previously published.  What am I missing?  Thanks.

Any ideas on this?  Anybody?  Please?

I'm trying to prevent publishing forms to form libraries that allow users to step on each other.  My forms are all browser based, as we have different versions of InfoPath installed in our organization, plus a number of users that don't have Office at all.

Thanks for any help.

Any chance it is the same issue here?

I checked and re-did my UDC files just to make sure they didn't have any mixed cases in the path.  Then I created a small custom form that just submits the form with the check out or in buttons.  The form submits, but now when I open the form and try to use the check out button, it throws a 7893 error.  I've tried to find the SharePoint log where the error text might be, but to no avail.  I looked over all three servers in the farm, and no such error can be found.

 Any ideas?

Hi-

We've been working on improving this product offering and should have an update soon.

In the meantime, my recomendation is to follow the tutorial to create the XTP and UDC files. I've found that both UDCs and the XSN's manifest need to have their URLs updated. This can get messy (editing manifest). So the simpler approach is to just create the XTP and UDCs using the tutorial on this site.

Another common error that I've seen would be addressed by checking the URL of the file to be checked out. There's a rule that sets this value before the data connection gets executed. You could try to isolate that rule to double check that the URL is being set correctly. It might not be and that would explain the issue.

Hope this helps!

Thanks for the reply Ernesto.  Unfortunately, I first encountered the 7893 error after I had gone through the tutorial and built everything from scratch.  I'll go back to square one and see if the URL to the form is constructed properly.

I'll keep you posted.

OK, here's what I've found.

 I totally created the XTP from scratch using the Check In-Out tutorial that came with the XTP.  Everything works beautifully through Section 3 of the tutorial.  I run into issues with the aforementioned error in SharePoint when I try to deploy the template part to another form and use it there.  Apparently, the path somehow gets changed when it's added to InfoPath's controls.  If you look at the rules after it's been added to an existing form, the pageURL is different than what it was when first constructed and saved.  I tried matching them up physically and republishing in a test form, per Section 4, and still get the same error.

I'm attaching my test form for further review, I can't seem to upload the template part, as the site will only allow one file but it's the same as the tutorial.  I'm at a loss, as once I modified the Check Out pageURL rule to match what's in the template part, it appears the URL's are identical.

Thanks for your help.

Hi-

I've noticed that when the XTP gets added to the InfoPath form, the two rules that set the pageUrl get modified by InfoPath (don't ask me why!). I've found that I have to modify the rule in the XSN form template to add this back: xdXDocument:get-DOM()/

So this won't work: 

concat(substring-before(substring-after(processing-instruction()[local-name(.) = "mso-infoPathSolution"], 'href="'), 'Forms/template.xsn"'), my:FormName, ".xml")

But this should work:

concat(substring-before(substring-after(xdXDocument:get-DOM()/processing-instruction()[local-name(.) = "mso-infoPathSolution"], 'href="'), 'Forms/template.xsn"'), my:FormName, ".xml")

What are you getting for the pageUrl in your environment? Is it a valid URL? A relative path or absolute Url?

Once I added back xdXDocument:get-DOM()/ back into the Check Out and Check in rules, it looks like I'm getting an absolute URL.  It's still throwing the error. 

Is this all we know?:

TomRenfro:

"Invalid form template", with the text "Relative links to Data Connection Libraries located on different SharePoint site collection are not supported." 

Any other details about the error?

No, I've got that one solved.  I'm attaching a snapshot of the error.

Thanks.

Do you have access to the server to check for that correlation ID? At this point, we would benefit from any additional details, so having that info would be helpful.

If you don't have access to the server, could you ask your SharePoint administrator to find the log for this correlation ID?

Yes, I have access and we have 4 servers in the farm.  I've looked at the Windows logs and SharePoint logs and am unable as yet to locate an entry with a corresponding correlation ID.  Not sure where else to look.

As stated before, when supplying the URL explicitly in the pageURL field, it works just fine.  It's when the URL is supplied via the XPath formula it seems to have an issue.

Strange. SharePoint keep detailed logs on these correlation ids. Have you checked C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS?

OK, after checking all 4 server logs, I still can't find a viable log of an error entry.

However, here's something really interesting: If I add the explicit checkout example as noted in Section 3, step 8 of the instructions and run in Preview mode, it works.  It also works whether the form regardless of the library.

When I publish the form and try to use on the same library, I get the error using an explicit URL.  I get the error even if I reference a form XML in another library.  I'm attaching the form.  Keep in mind this is SharePoint 2010.