Loading...

Standard Directives

Custom Parameters @< Param >

Data Queries can be parameterized without filter linking. You can parameterize any part a custom SQL uery by adding @< Param > tags to it. A major difference between using filter directives and custom parameters to filter the returned data set from a query, is that you have to pass values to custom parameters, while it’s optional with filter directives. The reason for this is that InVision rewrites a query by injecting SQL fragments based on any filter directives, while a query with custom parameters is executed as is.

In addition, you must use custom parameters in Form Element load and save scripts, because filter directives cannot execute in that context while ensuring a unique row is loaded or updated / inserted.

A custom parameter is just a token added to a SQL expression.

Example

SELECT *
FROM MyTable
WHERE MyKey = @PKValue

contains the custom parameter @PKValue.

A value must be passed to @PKValue by using the SetParamValue function when invoking a request from a Workbook.


@CurrentUserUID

Returns the unique ID of the user account as registered in the user management system.


@CurrentUserFullName

Returns the full name of the user (FirstName + LastName) as registered in the user management system.


@CurrentUserEmail

This directive returns an Email of the user registered in the user management system.


@Language

Returns the language code specified for the currently logged in user. The token can be used in Data Queries invoked from a Workbook, and will be resolved at the server.


@LanguageTwoLetter

Returns the ISO 639-1 two letter language code for the currently logged in user. The token can be used in Data Queries invoked from a Workbook, and will be resolved at the server.


@LCID

Returns the Locale ID for the currently logged in user. The token can be used in Data Queries invoked from a Workbook, and will be resolved at the server. http://msdn.microsoft.com/nb-no/goglobal/bb964664.aspx


@CurrentSolutionID

Returns the id of the Solution.


@CurrentWorkProcessVersionID

Returns the id of the Work Process Version that the Solution belongs to. Note that this directive is only resolved if the object being executed is part of a Solution that belongs to a Work Process Version.