Nevron Vision for SharePoint Documentation
Building Dashboards / Parameters in SharePoint Pages / Custom Parameters in SharePoint Pages
In This Topic
    Custom Parameters in SharePoint Pages
    In This Topic

    Parameters can be consumed by any expression, as discussed in the Parameters topic. Since expressions are supported by nearly all properties of the Nevron SharePoint Vision webparts, this gives you the incredible flexibility to bind nearly all aspects of the webparts (including details for the data source connection) to interactive user choices and preferences. Nevron SharePoint Vision distinguishes between two types of parameters - custom and predefined. The predefined parameters are explained in the Parameters topic, so the topics in this folder focus on custom parameters.

    You can think of custom parameters as a set of custom variables that you declare for each SharePoint page, that needs to have dynamic data aggregation/data visualization abilities (i.e. be a real dashboard). It is important to understand that when we talk about custom parameters and Nevron Web Parts, we are always referring to the SharePoint page in which the webpart(s) that will use the parameters resides on.

    For the purpose of storing the custom parameters values for each user that currently browses the SharePoint page, Nevron SharePoint Vision implements custom session state management, that allows for parameter values to be recorded in medias, other than the standard ASP.NET Session State. The storage for custom parameters values can be controlled globally, though the The WebParts Config File .

    Nevron SharePoint Vision provides three ways to create and modify custom parameters:

    1. With SharePoint Filter WebParts. See Custom Parameters with SharePoint Filter WebParts for more info.

    2. With Nevron JavaScript. See Custom Parameters with Nevron JavaScript API for more info.

    3. With Jump To Report Actions. See Actions and Drill Down reports for more info.

    Methods 1 and 2 help you declare a static for the page set of parameters and provide the user with the visual means to modify these parameters values.

    Method 3 (Action Type set to JumpToReport) is implementing a sophisticated browser redirection technique, that lets you modify a set of custom parameter values for the current user session for the action target URL, prior to the browser being redirected to that page, which is the heart of drill down reporting.

    See Also