It is – just add the Source= parameter to the end of the URL, and that will be the page that will be opened when the form is closed.
How to: Use Query Parameters to Invoke Browser-Enabled InfoPath Forms
There are four methods for invoking an InfoPath form or a browser-based version of the form on a server running InfoPath Forms Services. These methods consist of URLs that reference a form template file (.xsn), URLs that reference a form file (.xml) based on a form template, URLs that reference the built-in FormServer.aspx Web page, and those that contain a reference to a custom page containing theXmlFormView control. The first three types of URL support using query parameters to control aspects of the resulting form, including whether it will be opened in the InfoPath client or rendered in the browser, the location where the form will be saved, and the Web page that the user will be directed to when they close the form.
By default, InfoPath forms will open in InfoPath even if a browser-enabled form is available. If InfoPath is not installed, the form will open in the browser. In addition to using query parameters to control how forms are opened, SharePoint library settings are used to control where forms are opened. To always force the form to open in the browser, choose Display as a Web page on the library’s Advanced Settings page.
There are nine different parameters that can be used for opening InfoPath forms. Some parameters override others or cannot be used together, as noted in the table below. Name/value pairs other than those listed in the following table are interpreted as Input Parameters and passed to the form. Input parameters consist of one or more name/value pairs separated by the ampersand (&) character that are specified when a form template is opened from the command line or a batch file using the/InputParameters command-line option, or when a form template is opened from a URL. For more information about using input parameters, see theInputParameters property of theLoadingEventArgs class.
Parameter NameDescriptionAllowed Values
Used to open an existing form. TheXmlLocation andXsnLocation properties are mutually exclusive; specifying values for both parameters will result in an error.
A valid URL to a form file (.xml) in the same site collection.
Used to open a new form based on a form template. If anXsnLocation is specified in a URL using FormServer.aspx, aSaveLocation should also be specified if the Save and Save As buttons need to be displayed. TheSource parameter should also be specified or the message “”The form has been closed”” will appear when the user closes the form. TheXmlLocation andXsnLocation properties are mutually exclusive; specifying values for both parameters will result in an error.
A valid URL to a form template file (.xsn) published on the same site collection.
If aSource query parameter is specified, the default value isBrowser.
IfXmlLocation is specified, the default value is the setting used in the library.
If onlyXsnLocation is specified, the default value isPreferClient.
IfMobile is specified, the form will be redirected to the MobileFormServer.aspx page for rendering. The form template must be enabled for mobile support or an error message will be returned.
The location to which the user will be redirected when the form is closed. The URL must be in the same site collection or an error will be returned.
A valid URL in the same site collection as the form.
DisableSave is the only allowed value. It hides the Save and Save As buttons and disables saving the form when it is rendered in the browser.
A Save As dialog box is displayed prompting the user for a filename, and then it is saved in the specified folder. An error is returned if the specified folder does not exist.
Any valid folder location on the site collection.
Does not redirect to FormServer.aspx for client detection or rendering in the browser. Default value is false. If true and anXmlLocation orXsnLocation is specified, a File Download dialog is displayed when using Internet Explorer.
TheOpenIn parameter should be used instead, and overrides theDefaultItemOpen parameter value. A value of0 indicates that the request is from a document library and the InfoPath client was not detected. A value of1 indicates that the request is from a document or form library that has the Display as a Web page setting.
The query parameters and their associated values are not case-sensitive, but the corresponding properties of the XmlFormView control, such as theOptions andSaveLocation properties, are case-sensitive.Procedures
The following procedures require a site collection that you can publish form templates to, and the ability to create new sites in the site collection.
Placeholder values are used in the example URLs below. These values represent the following SharePoint and InfoPath items:
ServerName: A server running InfoPath Forms Services.
SiteCollection: The top-level site in a site collection.
FormLibrary: A form library or document library containing a browser-enabled form template.
Form1.xml: A form based on the template.xsn in FormLibrary.
NewFolder: A folder within the FormLibrary.
NewSite: A site within the SiteCollection.
The~sitecollection value used in the following URLs is not a placeholder value. It is a special token used with InfoPath Forms Services that enables relative links and site collection-scoped URL addresses.Using a URL with the XmlLocation parameter
Create a form template and upload it to a new form library.
Create a form based on that form template and save it as “”Form1″” in the library.
Enter the following URL, inserting actual values for the placeholder values: