Data Connection relative to site - InfoPath Dev
in

InfoPath Dev

Data Connection relative to site

Last post 07-12-2012 06:13 AM by Gennady Vanin (Геннадий Ванин, Новосибирск). 7 replies.
Page 1 of 1 (8 items)
Sort Posts: Previous Next
  • 07-08-2012 06:37 PM

    Data Connection relative to site

    I'm creating a site in SP2010 which will ultimately be saved as a site template for future use.
    In this site is a forms library with a browser enabled form. The desired submit option is to publish to the library where the template lives.
    This is all fine for the site I'm currently creating but later, when any future sites are based on this template the site name will not be the same.

    Is it possible to just tell IP that I'll be submitting to the library where you are hosted without having to specify the absolute path?

    Does that make sense?

  • 07-09-2012 05:15 AM In reply to

    Re: Data Connection relative to site

    My understanding is that when the submit-type data connection is created, the submit URL is hardcoded, and the only way to modify it would be by running the data connection wizard again to modify the data connection. I assume something could be done via code (or qRules) but that would not be an option in out-of-the-box-InfoPath.

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


  • 07-09-2012 01:15 PM In reply to

    Re: Data Connection relative to site

    Thanks, does the entire URL have to be provided?

    If I'm understanding correctly then it would appear to be impossible to ever save a site as a template (which is what I ultimately want to do) that contains an infopath forms library?

  • 07-09-2012 01:41 PM In reply to

    Re: Data Connection relative to site

    Could I get around this by publishing the form as a content type? (something I've never done before so would have to research)
  • 07-09-2012 01:48 PM In reply to

    Re: Data Connection relative to site

    No, I don't think that a content type will address this. The limitation is in the InfoPath connection wizard. You have to provide a full URL. Notice how there's no option to use a formula, or a field from the form, etc. It's an absolute path URL.

    Sorry, I can't think of a workaround or solution.


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


  • 07-09-2012 01:56 PM In reply to

    Re: Data Connection relative to site

    ok thanks... seems a bit of a limitation.

    How would a vendor include an infopath form as part of their solution or even a form itself if the site/library it was destined for couldn't be parameterised or self referenced.
    Even stranger when you consider that a forms library can be created and specified as an infopath library before you even start looking at infopath designing. You'd have thought someone at MS would have included a way to specify me/this/current library/other as data connection options for a newly created template.

    Time to dream up a plan B :)

  • 07-11-2012 02:24 PM In reply to

    Re: Data Connection relative to site

     The Document Library field in the data connection wizard? No, it does not allow data input other than typing in (no functions, no xpaths).

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


  • 07-12-2012 06:13 AM In reply to

    Re: Data Connection relative to site

     

    Jay@Work:
    How would a vendor include an infopath form as part of their solution or even a form itself if the site/library it was destined for couldn't be parameterised or self referenced

    If Microsoft is that vendor, then, I've got the impression from his answer to my question

    in order to run msdn's labs/lessons, that he doesn't know himself

    Gennady Vanin (Novosibirsk) --- Геннадий Ванин (Новосибирск)
Page 1 of 1 (8 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.