Assessing InfoPath 2007/2010 with SharePoint 2007/2010 Multi-Environment Deployments - InfoPath Dev
in

InfoPath Dev

Assessing InfoPath 2007/2010 with SharePoint 2007/2010 Multi-Environment Deployments

Last post 04-09-2012 06:08 AM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 04-02-2012 10:17 AM

    Assessing InfoPath 2007/2010 with SharePoint 2007/2010 Multi-Environment Deployments

    Hi all, We are currently assessing the viability of using InfoPath 2007 and 2010 within SharePoint 2007 and 2010 in a more controlled IT environment (e.g.: multiple deployment environments). We're hitting a few roadblocks when it comes to deploying InfoPath to multiple environments and are looking for guidance/best-practices. Our current situation is as follows:

    1) We'd like to develop our InfoPath form locally in the developer's machine using the developer's SharePoint local instance. (Let's call this environment as LOCAL).

    2) We'd like to deploy the InfoPath form to a TEST environment for QA to test before we graduate the form to the PRODUCTION environment.

    3) Some of the data may come from an XML file, a SharePoint List, a SharePoint Workflow, etc and all of them are well-prepared in the various environments mentioned above: LOCAL, TEST, PRODUCTION.

    4) ... and don't forget to submit to the right target (document library, list, etc) regardless of the environments

    We'd like to know how we can deploy the InfoPath form independent of the environment.

    ... and to extend the question: can someone refer us to an article that explains InfoPath best practices that covers making re-usable form templates (or sub-forms) with independent data source?


    Thanks!
  • 04-09-2012 06:08 AM In reply to

    Re: Assessing InfoPath 2007/2010 with SharePoint 2007/2010 Multi-Environment Deployments

    InfoPath 2007 and 2010 can coexist.

    Why are you employing developers to make LOCAL changes? Your InfoPath forms shouldn't have code in them (or they should leverage a common library which can be injected without visual studio).

    So, it's not hard. just use 2010 set to 2007 compatibility and evict the dev-heads.

    Life is easy.

    Patrick Halstead
    Project Manager at Qdabra
Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.