How to link to a web-enabled IP form from a dataview - InfoPath Dev
in

InfoPath Dev

Now you can find InfoPathDev on YouTube and Twitter!

How to link to a web-enabled IP form from a dataview

Last post 06-24-2009 06:24 PM by warrtalon. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 06-24-2009 03:31 PM

    How to link to a web-enabled IP form from a dataview

    I'm creating a dataview page in SP Designer for my Infopath form library and I need to add links to the forms.  Every variation of the URL I've tried trys to open the form in the client and not thru the browser.  If I'm in the library itself or if I use the dataview webparts, all is well, but niether of these options will serve my purposes so I have to do a dataview in SPD.

    What am I missing here?

    IP 2007 and SP MOSS 2007.

    Thanks!

  • 06-24-2009 03:38 PM In reply to

    Re: How to link to a web-enabled IP form from a dataview

    The links to the XML files are different than the links to the file in Forms Services.  Go open a form in the browser and notice the URL.  That is the URL you have to dynamically generate in your data view, not just the direct link to the XML file, which will always open in the rich client unless the user doesn't have IP07 (in this case, it does default to the browser).

    Now, what do you mean when you say dataview and dataview web parts?  I don't know of a difference. You said dataview webparts work but not "dataview."  I only know of one "dataview" entity in SPD, and that's the DVWP that you put on a page to show data in a formatted manner from one or many data sources.

  • 06-24-2009 04:03 PM In reply to

    Re: How to link to a web-enabled IP form from a dataview

    I've seen the term Dataview used interchangably for the 2 different ways so here's the differences: one is when you edit a page in SP, click add a webpart and you and you pick a view of a list or library...that is NOT the one I'm doing.  The one I'm doing is where you create/edit a page in SPD, and do an insert dataview, and you can mess with the xslt.  What I've got is my fields coming in from the form library and then I want a hyperlink (an image or clickable words like "View Form") that opens up the corresponding form in the browser.

    You mentioned that I have to dynamically generate the URL and maybe that's where I'm getting messed up.  Do you have a sample piece of code for that you can share?

  • 06-24-2009 05:16 PM In reply to

    Re: How to link to a web-enabled IP form from a dataview

    Updated below......Ok, I still can't figure out how to build the URL in the dataview code so I have a workflow building the URL and updating the record and I'm using that in my dataview...this works just fine.  What I'm finding is that the URL in the library is correct, but when it comes thru from the form it's changing the ampersands from just & to & that's causing my links to not open the form in the browser.  I know I've now strayed from Infopath and into xslt but if anyone has a page where they've hyperlinked to a browser-based form successfully, please share the code block.

     Here's the code block:

    <td class="style1"><a href="https://[url to library]/_layouts/FormServer.aspx?XmlLocation={@FileRef}&amp;Source=[url to return to when finished]&amp;DefaultItemOpen=1">view</a></td>

  • 06-24-2009 06:24 PM In reply to

    Re: How to link to a web-enabled IP form from a dataview

    I don't use code in my forms, but I am able to dynamically build this link pretty easily with anything that lets me concatenate static text with metadata (from the form).  I can do this within the form itself (consider that as an extra data field that you can then expose in the dataview or use as a source for your "View Form" text) or within SharePoint Designer with the Dynamic STring Builder.  Doing it these ways has no issues with characters getting converted.

    Yes, you are using Data View Web Parts (DVWP).  I don't consider the other thing a data view at all.

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