For each report you need to create a data source from which to read the report data to be displayed. Normally one data source is sufficient for one report. However, you can define several data sources for each report.
To edit a data source
- OR -
Click Add.
This creates a new data source.
To delete a data source
You can test the results while processing a data source.
To test a data query
The result of a data source is shown in a separate dialog.
|
NOTE: When a data query is copied to the clipboard, a database query is generated in SQL syntax, which you can run on the database with an appropriate SQL query tool. To copy the data query, use the |
Data queries with the SQL query module are executed directly on the database without checking user access permissions. This means that a column to be used in the report is displayed even though the user may not have access permission to it.
Property | Meaning |
---|---|
Name | Name of the data source. |
Description | Description of data source. |
Max. lines |
Maximum number of result lines for this query. If this number is exceeded, report creation is terminated. |
Parent query |
Not used. |
Query module | Select the SQL query module. |
Query |
Full database query SQL syntax. The query must contain all the columns used in the report. You can also use SQL parameters in the query. Add these parameters subsequently to the report by entering them on the Parameters tab. Syntax for parameters: @<Parametername> |
The query should return the employees (table Person) assigned to an department. The department (UID_Department) is found with (XObjectKey). This is passed as a parameter to the report. The employee‘s first name (firstname), last name (lastname) and department name (departmentname) are queried.
Select Firstname, Lastname, Departmentname
from person join Department
on person.uid_Department = department.uid_Department
where Department.XObjectKey = @ObjectKeyBase
You can use the View query module to create data queries using predefined database views and thus control user access rights.
Property | Meaning |
---|---|
Name | Name of the data source. |
Description | Description of data source. |
Max. lines |
Maximum number of result lines for this query. If this number is exceeded, report creation is terminated. |
Parent query |
Not used. |
Query module | Select the View query module. |
View name | Name of the database view. |
Condition |
Condition for limiting the data set returned from the database table. You formulate the condition as a valid WHERE clause for database queries. You may use SQL parameters in the condition. Add these parameters subsequently to the report by entering them on the Parameters tab. Syntax for parameters: @<Parametername> |
Sort order | The data queries are sorted by these database view columns. |
Data queries with the Object query module are created using the object layer and therefore take user access permissions fully into account.
Property | Meaning |
---|---|
Name | Name of the data source. |
Description | Description of data source. |
Max. lines |
Maximum number of result lines for this query. If this number is exceeded, report creation is terminated. |
Parent query |
In a parent query, restrictions are applied to the data record that are passed on to subsequent queries, all members of a department, for example. Parameters that are defined in the parent query are also available in subsequent queries. |
Query module | Select the Object query module. |
Table | Select the table to find the object in. |
Columns |
Columns to use in the report. Some columns are always added to the report definition and must not be explicitly entered here. These include:
|
Resolve foreign key | Set this option if the display value of the referenced object should be returned in <column>_Display rather than the UID. |
Condition |
Condition for limiting the data set returned from the table. You formulate the condition as a valid WHERE clause for database queries. You may use SQL parameters in the condition. Add these parameters subsequently to the report by entering them on the Parameters tab. Syntax for parameters: @<Parametername> Syntax for columns of a parent query: @<name of parent query>.<column of the parent query> |
Sort order | The data queries are sorted by these table columns. |
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy