Page History
...
Expand | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
If the Value List Setup option is set to Custom Query or the following options will become available. The following tokens can be used within SQL to filter queries under certain circumstances: When using a Cached Query, the SQL can include the following tokens: %CLIENTREFID% - This will insert the client reference Id into the SQL. This should only be used when client source substitution is used, where data for multiple clients may exist in a single database. When using a Cached Query on Demand and a source filter is enabled, the SQL can include these tokens: %CLIENTREFID% - This will insert the client reference Id into the SQL. %REFERENCE_TYPE% - This will insert the Access Filter values for the user who is running a report. For example, an Access Filter reference code named REGION, will have a token named %REGION%. Access Filter values will be inserted as text tokens and will be quoted in the generated SQL. Multiple tokens will be inserted in comma-separated form, so that they can be included in an SQL IN statement. %REFERENCE_TYPE_NUMERIC% - This will insert the Access Filter values for the user who is running a report. For example, an Access Filter reference code named USERID, will have a token named %USERID_NUMERIC%. Access Filter values will be inserted as numeric tokens. Multiple tokens will be inserted in comma-separated form, so that they can be included in an SQL IN statement. |
...