DBXL Migration Tool - Import - InfoPath Dev
in

InfoPath Dev

DBXL Migration Tool - Import

Last post 04-16-2012 07:33 AM by ErnestoM. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 04-11-2012 01:57 PM

    DBXL Migration Tool - Import

    How do I get the DBXL Migration Tool to import my documents by the correct filename?  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 within DBXL and in my SharePoint library.  I've looked at all of the mapping files but can't find where to set the import filename convention.
  • 04-12-2012 05:45 AM In reply to

    Re: DBXL Migration Tool - Import

    Hi-

    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're asked to define a DBXL::Name token. That'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.

    Can you check your data connection and see how the DBXL::Name is defined? Let us know. Thanks!

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 04-12-2012 10:40 AM In reply to

    Re: DBXL Migration Tool - Import

    Ernesto,

     My data connection has the correct xpath listed for the name token.  The IP form works properly when submitted and creates the correct xml filenames.

    For example, right now, all of my documents are xxx-xxx-xxxx.xml within my sharepoint library and in dbxl.  If I export them, the exported files are the <docid>.xml and no longer xxx-xx-xxxx.xml.  Not really a problem, I whip up a vb script to parse the xml file and rename it based on social.  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 <docid>.xml both within DBXL and SharePoint.

    I've got 9000 documents to import and they need to be xxx.xx.xxxx.xml not <docid>.xml

    Thank you...

    Ed

  • 04-16-2012 07:33 AM In reply to

    Re: DBXL Migration Tool - Import

    Hi Ed-

    Thanks for the additional info. What I expect is the following:

    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.

    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).

    After import, try the following and then check the SharePoint form library:

    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?

    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?

    Thanks.

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.