Qdabra Database Accelerator

Re: Updated from 2.4 to 2.6, SharePoint form name is different.

ErnestoM — Wed, 03 Oct 2012 12:23:29 GMT

Hi John,

I'm sorry you've run into this. Feel free to contact us via support at qdabra dot com. For customers performing an upgrade, we typically offer some help so that issues (such as this) can be identified. I'm not guaranteeing we would've caught this, but we would've tried to identify potential issues with the upgrade. :)

So yes, the SharePoint-DBXL interaction requires that the DBXL::Name (which goes into the Title column) have a unique value.

If the value is not unique, DBXL appends the DocID.
If the DBXL::Name is not defined, then the DocID is used; of course, that leaves the DBXL::Name blank in the Documents tab in DAT.

Let me suggest a third option which may work for you. I think the change was included in late versions of DBXL v2.6, and it is definitely included in the upcoming DBXL v2.7.

You can add a setting in web.config to modify the way DBXL maps XML forms to SharePoint. If the key is set to true, the DBXL::Name is ignored and the DocID is used instead. This is not, by default, included in DBXL’s web.config and must be manually added above the closing appSettings tag.

<add key="UseDocIdForSharePointFileName" value="true" />
<add key="UseDocIdForSharePointFileName-YourDocTypeNameHere" value="true" />

This would allow you to have a DBXL::Name defined, and use the DocID as the Title column in the SharePoint form library.

Let me know whether that addresses that issue.

As far as the shredding error, can you provide more info on this? Maybe check the eventvwr Qdabra log to see if there are any additional details. Thank you.

Re: Updated from 2.4 to 2.6, SharePoint form name is different.

JohnLiu — Wed, 03 Oct 2012 06:56:31 GMT

http://www.infopathdev.com/files/folders/installation_and_setup/entry74630.aspx says:

SHAREPOINT MAPPINGS AFTER UPGRADING DBXL

This applies to users that have an existing SharePoint mapping with a previous version of DBXL. SharePoint mapping has been updated to use the DBXL::Name token at the Title in SharePoint. If no DBXL::Name token is declared, then DBXL will use the DocID. In addition, DBXL v2.6 will promote some additional columns. After upgrading DBXL, verify that open and submit works for existing documents without issues, then perform a Reshred All to update to the new promoted columns

This is a pretty devastating change for us. The result is that we may have to go back to 2.4 if we can't specify a way to use DocID for filename.

For people that are stuck, we're currently going with the no DBXL::Name token in the service call.

To remove the argument in your InfoPath form:

publish to source files, then open the manifest file and look for the submit connection dataadapter. Remove the entire line for the tns:Name argument. Re-publish.

But now in DBXL all the new forms don't have a name, also, existing forms can't be reshredded, since they already have a name... ouch.

Updated from 2.4 to 2.6, SharePoint form name is different.

JohnLiu — Wed, 03 Oct 2012 06:10:17 GMT

in 2.4, the name of the form stored in SharePoint document library used to be the DocID of the form submitted to DBXL.

in 2.6, the name of the form is now the "name" property that we specify when submitting to DBXL.

But DBXL also adds additional DocID in the form of "MyForm (1455)".

Iis there a way to configure DBXL so that it uses the DocID of the form for the filename, as per the behaviour back in 2.4 - that guaranteed a level of uniqueness.