<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Qdabra Tools</title><link>https://www.infopathdev.com:443/forums/135.aspx</link><description>Community support for Qdabra tools, including Bulk Edit Tool, Bulk Reassignment Tool, Document Deployer, UDC Editor Tool, LDAP test tool, QdUpgrade WinForm Tool, Query Builder, Excel to XML tool, InfoPath to ShP List Tool and EmailBuilder.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: DBXL Migration Tool - Import</title><link>https://www.infopathdev.com:443/forums/thread/77607.aspx</link><pubDate>Mon, 16 Apr 2012 14:33:56 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:77607</guid><dc:creator>ErnestoM</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/77607.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=135&amp;PostID=77607</wfw:commentRss><description>&lt;p&gt;Hi Ed-&lt;/p&gt;&lt;p&gt;Thanks for the additional info. What I expect is the following:&lt;/p&gt;&lt;p&gt;1. You submit a document and it is named in the SharePoint form library as xxx-xxx-xxxx.xml (because your DBXLDocumentService submit data connection sets this as the DBXL::Name). Sounds like this is working correctly.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;2. You export the documents, and then import them. (I believe the local file name after export does not matter.) Documents will get assigned a new DocID as they are imported, but the DBXL::Name should not change. That is, after import I would expect them to retain the same name (xxx-xxx-xxxx.xml) in the SharePoint form library (unless there are duplicates in DBXL::Name).&lt;/p&gt;&lt;p&gt;After import, try the following and then check the SharePoint form library:&lt;/p&gt;&lt;p&gt;a) reshred one document that was imported. This can be done via the DBXL Admin Tool. Does the name change from the DocID to xxx-xxx-xxxx.xml?&lt;/p&gt;&lt;p&gt;b) Submit a new document (in the location of the import). Does it get submitted with DocID as the name or xxx-xxx-xxxx.xml?&lt;/p&gt;&lt;p&gt;Thanks. &lt;br /&gt;&lt;/p&gt;</description></item><item><title>Re: DBXL Migration Tool - Import</title><link>https://www.infopathdev.com:443/forums/thread/77530.aspx</link><pubDate>Thu, 12 Apr 2012 17:40:12 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:77530</guid><dc:creator>emcandrew2</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/77530.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=135&amp;PostID=77530</wfw:commentRss><description>&lt;p&gt;Ernesto,&lt;/p&gt;&lt;p&gt;&amp;nbsp;My data connection has the correct xpath listed for the name token.&amp;nbsp; The IP form works properly when submitted and creates the correct xml filenames.&lt;/p&gt;&lt;p&gt;For example, right now, all of my documents are xxx-xxx-xxxx.xml within my sharepoint library and in dbxl.&amp;nbsp; If I export them, the exported files are the &amp;lt;docid&amp;gt;.xml and no longer xxx-xx-xxxx.xml.&amp;nbsp; Not really a problem, I whip up a vb script to parse the xml file and rename it based on social.&amp;nbsp; BUT, if I then re-import those documents (named xxx-xx-xxxx.xml) using the DBXL Migration Tool, then all of the documents are assigned a new document ID within DBXL and subesquently named &amp;lt;docid&amp;gt;.xml both within DBXL and SharePoint.&lt;/p&gt;&lt;p&gt;I&amp;#39;ve got 9000 documents to import and they need to be xxx.xx.xxxx.xml not &amp;lt;docid&amp;gt;.xml&lt;/p&gt;&lt;p&gt;Thank you...&lt;/p&gt;&lt;p&gt;Ed&lt;/p&gt;</description></item><item><title>Re: DBXL Migration Tool - Import</title><link>https://www.infopathdev.com:443/forums/thread/77508.aspx</link><pubDate>Thu, 12 Apr 2012 12:45:42 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:77508</guid><dc:creator>ErnestoM</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/77508.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=135&amp;PostID=77508</wfw:commentRss><description>&lt;p&gt;Hi-&lt;/p&gt;&lt;p&gt;DBXL defines the filename in the data connection that submits to DBXL. That is, your form probably already has a data connection that submits to the DBXLDocumentService. In that data connection, you&amp;#39;re asked to define a DBXL::Name token. That&amp;#39;s the name that is displayed in the Documents tab in the DBXL Admin Tool and also used as the Title column if your document type has a SharePoint mapping.&lt;/p&gt;&lt;p&gt;Can you check your data connection and see how the DBXL::Name is defined? Let us know. Thanks! &lt;br /&gt;&lt;/p&gt;</description></item><item><title>DBXL Migration Tool - Import</title><link>https://www.infopathdev.com:443/forums/thread/77481.aspx</link><pubDate>Wed, 11 Apr 2012 20:57:48 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:77481</guid><dc:creator>emcandrew2</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/77481.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=135&amp;PostID=77481</wfw:commentRss><description>How do I get the DBXL Migration Tool to import my documents by the correct filename?&amp;nbsp; In my scenario my xml filenames are social security number format (xx-xxx-xxxx.xml), but every time I import them using the migration tool, they assume the docID as the filename&amp;nbsp;within DBXL and in my SharePoint library.&amp;nbsp; I&amp;#39;ve looked at all of the mapping files but can&amp;#39;t find where to set the import filename convention.</description></item></channel></rss>