What are ramifications of moving a DBXL form to a different library after it's been DB and SharePoint mapped? - InfoPath Dev
in

InfoPath Dev

What are ramifications of moving a DBXL form to a different library after it's been DB and SharePoint mapped?

Last post 06-20-2013 12:15 PM by Doreen. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 06-19-2013 10:00 AM

    • Doreen
    • Top 50 Contributor
      Female
    • Joined on 08-11-2010
    • Federal Way, WA
    • Posts 291

    What are ramifications of moving a DBXL form to a different library after it's been DB and SharePoint mapped?

    I assume the database mapping will always follow the form but I also assume the SharePoint library mapping will break?  Is this true? 

    I have a form template that will be submitted to one SharePoint (2007) library.  User wants to create other document libraries to archive the form into when she's finished with the forms.  Will this break the form?

    I assume she can "safely" create folders in the existing library to move them into as an alternative?

    Filed under:
  • 06-19-2013 12:02 PM In reply to

    Re: What are ramifications of moving a DBXL form to a different library after it's been DB and SharePoint mapped?

    Hi Doreen,

    I don't think manually creating folders and then manually moving the XML files is a good idea. Users make mistakes, so it's best to control what they can and cannot do. As the form designer, you can control this with some simple changes. Basically, you would allow DBXL to control the SharePoint mapping, via a conditional mapping.

    Your document type would have two SharePoint mappings, each with its own condition. For example

    http://<myserver>/<myACTIVElibrary>

    Condition: my:status = 'Active'

    http://<myserver>/<myINACTIVElibrary>

    Condition: my:status = 'Inactive'

    Within the form, you would have a simple status field (Active vs. Inactive). Its value will then control whether the form is mapped to the Active library or the Inactive library.

    The database mapping is not affected by any of this.

    Hope this helps!

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


  • 06-19-2013 04:45 PM In reply to

    • Doreen
    • Top 50 Contributor
      Female
    • Joined on 08-11-2010
    • Federal Way, WA
    • Posts 291

    Re: What are ramifications of moving a DBXL form to a different library after it's been DB and SharePoint mapped?

    Okay thanks Ernesto that makes sense.

    You are talking about mapping between libraries.  What about moving an item (forms) from the root library to one or more folders in the same library?  Does that make any difference wtih the SharePoint mapping?

  • 06-20-2013 05:56 AM In reply to

    Re: What are ramifications of moving a DBXL form to a different library after it's been DB and SharePoint mapped?

    DBXL doesn't have the ability to map forms to subfolders within libraries, sorry.

    If the users will be moving the files manually to subfolders, I'm not sure how that's going to affect the SharePoint mapping. It would be a good test, but it's never come up before. Let us know what you find!

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


  • 06-20-2013 12:15 PM In reply to

    • Doreen
    • Top 50 Contributor
      Female
    • Joined on 08-11-2010
    • Federal Way, WA
    • Posts 291

    Re: What are ramifications of moving a DBXL form to a different library after it's been DB and SharePoint mapped?

    Wow, really? I guess I'll be your guinea pig. :I
Page 1 of 1 (5 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.