How to: Deploy a .UDCX file to a Data Connection Library

re: How to: Deploy a .UDCX file to a Data Connection Library

n0ext — Wed, 25 Aug 2010 10:26:15 GMT

Download the .udcx file, delete the sharepoint one and upload the previously downloaded back. You can now specify the Title and do the Check-In (you could also modify the file parameters such as the connection string if necessary).

re: How to: Deploy a .UDCX file to a Data Connection Library

Pascal van Alphen — Tue, 23 Mar 2010 15:18:55 GMT

The Title field not being filled does matter. If you change or upload a new version of a UDCX to the Data Connection Library, and then want to Check In that file, SharePoint doesn't allow it: the Title is a required field. This check is ignored with feature activation, but not with a manual change.

Most annoying thing about this: manually entering the Title doesn't seem to work either.

re: How to: Deploy a .UDCX file to a Data Connection Library

CoreyRoth — Tue, 01 Dec 2009 15:14:04 GMT

I've actually run into the Title field not being populated before as well. For some reason it doesn't pick it up from the CAML. However, it does not affect the usability of the .udcx file.

re: How to: Deploy a .UDCX file to a Data Connection Library

Camilo Vergara — Tue, 01 Dec 2009 15:00:04 GMT

How can I fix the empty title issue?

re: How to: Deploy a .UDCX file to a Data Connection Library

CoreyRoth — Tue, 06 Oct 2009 14:38:15 GMT

GuyO.

Actually I have discovered you can specify the list name for a SharePoint List in a .UDCX. CHeck out this post.

www.dotnetmafia.com/.../specifying-a-list-by-name-in-a-udcx-file.aspx

re: How to: Deploy a .UDCX file to a Data Connection Library

GuyO — Tue, 29 Sep 2009 15:22:06 GMT

I just discovered another reason for doing all of this in CAML vs a feature handler -- MSDN Article 931414 -- it's not possible to update the title of a udcx file after it has been deployed; so it has to be done in CAML as shown above.

re: How to: Deploy a .UDCX file to a Data Connection Library

GuyO — Fri, 18 Sep 2009 12:29:58 GMT

This works well. - Until the connection is to a Sharepoint List. -- unlike column lookups in a sharepoint feature, infopath isn't smart enough to fix up a lists/foo reference. I have been able to fix up the ListID Guid references using a featureEvent handler. I just finished testing the and deploying the solution and as soon as I can get it "cleaned" up for publcaton, I'll post the link,