Previous Topic  Next Topic

Parameter Application Cases

In Logi Report, you can apply parameters in many situations. The usage of parameters can greatly facilitate your reporting work. This topic shows some typical parameter application cases.

This topic contains the following sections:

• Dynamically Filtering Queries
• Dynamically Grouping/Sorting Report Data
  • Grouping Data Dynamically
  • Sorting Data Dynamically
• Filtering a Parameter with Another Parameter
• Controlling Multiple Parameters in a Report
• Applying RLS to Parameters
• Supplementing WHERE Portions

Dynamically Filtering Queries

You can use a parameter in a WHERE clause, so that the query result can vary each time according to the specified parameter value. This is the most common usage of parameters.

The feature works the same for Logi Report queries created using the Query Editor, business views, datasets, imported SQLs, and imported APEs (it is $match stage instead of WHERE clause for APE). When using imported SQL, you just need to add @Parameter or :Parameter Name in the SQL statement; for imported APE, add @Parameter or ?Parameter Name in the JSON file to be imported. Designer provides the default values when you import the file so the database recognizes the syntax.

The following example shows using a parameter to filter a Logi Report query dynamically.

1. Make sure SampleReports.cat is the currently open catalog file. If not, navigate to File > Open Catalog to open it from <install_root>\Demo\Reports\SampleReports.
2. In the Catalog Manager, expand the node of the data source where you want to add the parameter, then create a type-in parameter IDSet of Integer type with the default values 1, 10, and 20, and enable the Allow Multiple Values option.
3. In the same data source, create a queryCustomersInfo on the table Customers. Select all the fields contained in the table.
4. In the Query Editor dialog box, navigate to Menu > Query > Filter.
5. Filter the records of the query by adding a condition as follows in the Search Condition dialog box.

   

6. Create a page report with a table in it based on the query, which displays the fields Customer ID, Customer Name, City, and Phone and applies the Commercial style.
7. Select the View tab to preview the report.
8. In the Enter Parameter Values dialog box, select next to the value text box of IDSet.
9. In the Enter Values dialog box, clear All Values, add the listed values 1, 10, and 20 to the Selected Values box, and then select OK.
10. Select OK in the Enter Parameter Values dialog box. Designer retrieves the records with Customer IDs equal to 1, 10, and 20 for the table.

    

11. Preview the report again. This time, in the Enter Values dialog box, remove 1, 10, and 20 from the Selected Values box first, then type the values 3, 7, 9, 11, 15, and 25 in the Enter Values text box and add them into the Selected Values box one by one.
12. After you submit the parameter values, the table now displays the records for the specified Customer IDs.

    

13. If you want to view the table with full data, select All Values in the Enter Values dialog box.

• You need to specify the parameter's data type according to the field type and the manner in which you use the parameter. For example, if the field is a number, define a parameter of the Number type too.
• When specifying the value for a parameter used in a filter condition, if the parameter is String type,
  • When you use the parameter for a Logi Report query, imported SQL, business view, or dataset,
    • If you reference it in the format :ParameterName, the parameter value you type should be with single quotation marks, for example, 'USA'.
    • If you reference it in the format @ParameterName, the parameter value should be without single quotation marks, for example, USA. Once you type a parameter value with single quotation marks, Logi Report Engine regards the quotation marks as a part of the parameter value.
  • When you use the parameter for an imported APE, the parameter value should be with double quotation marks, for example, "USA".

  If the parameter is not of String type, you can type the parameter value directly, for example, 1234.

Dynamically Grouping/Sorting Report Data

An important usage of parameters is to use them to dynamically group and sort data in a report, which enables users to specify the grouping and sorting conditions at runtime.

The Dynamic Group and Dynamic Sort features only apply to tables and banded objects that use query resources in page reports.

Grouping Data Dynamically

You can make a multilevel group report by selecting a field as grouping criterion for the report. However, because the grouping criteria are definite, if you want to group several times according to different grouping criteria but based on the same query, it is cumbersome. For example, you want to make three employee list reports with different grouping criteria: the first one is grouped by their first name, the second one is by the hire date, and the third one is by their salary, then you have to repeat the steps of setting query, selecting fields as grouping criteria, and so on, which is not efficient. In cases like this, you can use the Dynamic Group feature of Designer, which means grouping criteria is a dynamic process. You do not need to repeat the same steps to make multiple reports with different grouping criteria. You can just predefine a parameter using String value type and add it to the group list. Then at runtime, when Logi Report Engine prompts users to select a field to group by, users can get all the acceptable group-by fields from the parameter's value drop-down list. They can select any of them as the grouping criterion.

The following example shows how you can create a table in a page report to achieve the goal.

1. Make sure SampleReports.cat is the currently open catalog file. If not, navigate to File > Open Catalog to open it from <install_root>\Demo\Reports\SampleReports.
2. Navigate to File > New > Page Report.
3. In the Select Component for Page Report dialog box, select the Table (Group Left Above) component type and select OK.
4. In the Data screen of the Table Wizard, select the query EmployeeInformation in Data Source 1. Select Next.
5. In the Display screen, add the following fields in the selected query to the table: Hire Date, Name, Home Phone, and Salary. Select Next.
6. In the Resources box of the Group screen, select <New Parameter...> in the Parameters node to create a type-in parameter pGroupBy of String type (leave the other settings to their default).
7. Specify to group the report on the just created parameter pGroupBy and use Ascend as the sorting order.

   

8. Select Finish in the Table Wizard to create the table.
9. Select the View tab to preview the report. Designer displays the Enter Parameter Values dialog box for you to specify the grouping criterion. The value drop-down list of the parameter contains all DBFields in the query the table uses and the valid formulas for these DBFields. Select the field by which you want to group data in the table.

   

10. Select Employee Position as the parameter value. Designer groups data in the table by positions of the employees.

    

11. To group the data by hire date or salary, select Hire Date or Salary from the value drop-down list of pGroupBy.

Sorting Data Dynamically

The following example shows how you can use the Dynamic Sort feature.

1. Make sure SampleReports.cat is the currently open catalog file. If not, navigate to File > Open Catalog to open it from <install_root>\Demo\Reports\SampleReports.
2. Navigate to File > New > Page Report.
3. In the Select Component for Page Report dialog box, select the Table (Group Above) component type and select OK.
4. In the Data screen of the Table Wizard, select the query EmployeeInformation in Data Source 1. Select Next.
5. In the Display screen, add the following fields in the selected query to the table: Hire Date, Name, Home Phone, and Salary.
6. Select Sort Fields By.
7. In the Sort Fields By dialog box, select <New Parameter...> in the Parameters node in the Resources box to create a type-in parameter pSortBy of String type (leave the other settings to the default).
8. Add the just created parameter pSortBy as the sort-by field.

   

9. Select Dynamic Sort from the sort order drop-down list in the Sort column.
10. In the Specify Sort Order for dialog box, type SortBy Order, then select OK to close the dialog box.

    

11. Select OK in the Sort Fields By dialog box to accept the changes.
12. Select Finish in the Create Table wizard to create the table.
13. Select the View tab to preview the table. Designer displays the Enter Parameter Values dialog box for you to specify the sort manner. The value drop-down list of the pSortBy parameter contains all DBFields in the query the table uses and the valid formulas for these DBFields . You can select a field by which to sort the data and then specify the sort order in the SortBy Order drop-down list.

    

14. Select Salary from the pSortBy list and DESCENDING from the SortBy Order list. Designer displays the records within each group in descending order according to their salary values.

    

15. Preview the table again and this time select Name from the pSortBy list and ASCENDING from the SortBy Order list. The table displays like this:

    

Filtering a Parameter with Another Parameter

You can use the value of one parameter to filter another one. In this way, you can create your own cascading parameters such as using pCountry to filter the values returned by a parameter listing available states.

The following examples show you the two methods you can use to achieve this purpose.

Method 1 (Use this method when the SQL needed to select the parameter values is very simple.)

1. Make sure SampleReports.cat is the currently open catalog file. If not, navigate to File > Open Catalog to open it from <install_root>\Demo\Reports\SampleReports.
2. In the Catalog Manager, expand the node of the data source where you want to add the parameter.
3. Right-click the Parameters node and then select New Parameter.
4. In the New Parameter dialog box, type CasParam in the Name text box, select Bind with Cascading Columns from the Value Setting drop-down list, and then select Customers of the Tables type from the Data Source drop-down list.
5. Select Add to add a parameter line, select Region as the Bind Column and Display Column, and then select in the Parameter cell to create the parameter in the cascading group.
6. Add another parameter line, select Country as the Bind Column and Display Column, and then select in the Parameter cell.
7. Add one more parameter line, select City as the Bind Column and Display Column, select in the Parameter cell, and then select OK in the dialog box.

   

8. In the same data source, create a queryCustomersInfo on the table Customers and select all the fields in the table.
9. Filter the records of the query by adding a condition as follows in the Search Condition dialog box.

   

10. Create a page report with a table in it based on the query, which displays the fields Customer Name, City, Country, and Region.
11. Select the View tab to preview the report.
12. In the Enter Parameter Values dialog box, select a region from the region drop-down list, Designer then only lists the countries in the selected region in the country drop-down list. Choose a country from the list, and you get the cities in the selected country in the city drop-down list only.

    

13. Select OK to apply the parameter values. You can find that the report only displays the specified records.

Method 2 (Use this method when you need more customized SQL to show the correct values.)

1. Make sure SampleReports.cat is the currently open catalog file. If not, navigate to File > Open Catalog to open it from <install_root>\Demo\Reports\SampleReports.
2. In the Catalog Manager, expand the node of the data source where you want to add the parameter.
3. Right-click the Parameters node and then select New Parameter.
4. Create a parameter ParamRegion, select Bind with Single Column from the Value Setting drop-down list, select Tables and Views from the Source drop-down list, select Region as the Bind Column and Display Column. Then in the value cell of the Import SQL option, you can see the following statement:

   Select DISTINCT CUSTOMERS.REGION FROM CUSTOMERS

   

5. Create another parameter ParamCountry. Bind it with the column Country, then select the ellipsis in the value cell of Import SQL and edit its SQL statement to:

   Select DISTINCT CUSTOMERS.COUNTRY FROM CUSTOMERS WHERE (Customers.Region=@ParamRegion and Customers.YTDSALES > 0 )

6. Create one more parameter ParamCity. Bind it with the column City, and then edit its SQL statement to:

   Select DISTINCT CUSTOMERS.City FROM CUSTOMERS WHERE (Customers.Country=@ParamCountry and Customers.YTDSALES > 0 )

7. In the same data source, create a query CustomersInfo on the table Customers, select all the fields in the table, and filter the records of the query by adding the following condition.

   CUSTOMERS.CITY=@ParamCity

8. Create a page report with a table in it based on the query, which displays the fields Customer Name, City, Country, and Region.
9. Preview the report.
10. In the Enter Parameter Values dialog box, you can use the value of ParamRegion to filter the value of ParamCounty, and use the value of ParamCounty to filter the value of ParamCity. You cannot see any countries and cities where there are no sales.

Controlling Multiple Parameters in a Report

When you use multiple parameters in a report, but you only want to show some of them when running the report, you can group them and then select the parameter you want for the report. Logi Report Engine automatically applies the default values for the parameters the values of which you do not specify.

The following example shows how you can control parameters in a report.

1. Make sure SampleReports.cat is the currently open catalog file. If not, navigate to File > Open Catalog to open it from <install_root>\Demo\Reports\SampleReports.
2. In the Catalog Manager, expand Data Source 1, then right-click the Parameters node and select New Parameter.
3. In the New Parameter dialog box, type GroupParam in the Name text box, select Parameters from the Value Type drop-down list, then add three parameters as the default values of GroupParam.

   

4. Open an existing page report.
5. Insert the parameters P_Category, P_Month, P_Country, and GroupParam into the report.
6. Select the View tab to preview the report. Designer displays the Enter Parameter Values dialog box for you to select the parameters for which you want to specify values.

   

7. Select @P_Category from the GroupParam drop-down list, Designer displays the P_Category parameter in the dialog box and you can select or type a value for the parameter. If you select @P_Month,@P_Country, Designer displays both the parameters P_Month and P_Country for you to specify values with which to run the report.

Applying RLS to Parameters

For parameters bound with DBFields, you can apply Record Level Security of data source scope to them. Logi Report Engine applies the security policy to the DBField that is bound with the parameter. At runtime, users will only see parameter values which the security identifier is allowed to view in the value drop-down list of the parameter.

The following example explains how you can apply RLS to the value drop-down list of a parameter.

1. Make sure SampleReports.cat is the currently open catalog file. If not, navigate to File > Open Catalog to open it from <install_root>\Demo\Reports\SampleReports.
2. In the Catalog Manager, expand the data source where you want to create the parameter.
3. Right-click Security Entry in the Security node, select New Security Entry on the shortcut menu, then name the security policy CusCountry.
4. In the Security dialog box, make sure Valid RLS is selected at the bottom left.
5. Select Add and select Add User. In the Add User dialog box, type John in the User text box and select OK.
6. In the Record Level Security tab, edit the security condition to grant John the permission to view records in Canada only.

   

7. Add another user David which has the permission to view records in the United Kingdom only.
8. Select OK to exit the Security dialog box.
9. In the same data source, right-click the Parameters node and select New Parameter on the shortcut menu.
10. In the New Parameter dialog box, type pCountry in the Name text box, select Bind with Single Column from the Value Setting drop-down list, and bind the parameter with the Country column. In the Options box, select CusCountry as value of Record Level Security, and then set Distinct to true. Select OK to create the parameter.

    

11. Create a queryCustomersInfo on the Customers table. Select all fields in the table.
12. Create a page report with a standard banded object in it based on the query, which displays the fields Customer ID, Customer Name, Country, and Phone.
13. In the Data panel, right-click the node that represents the query, and then select Edit Query from the shortcut menu.
14. In the Query Editor dialog box, navigate to Menu > Query > Filter.
15. In the Search Condition dialog box, add a condition for the query.

    

16. Select OK to apply the changes to the query.
17. Navigate to File > Options. Designer displays the Options dialog box.
18. In the General category of the dialog box, set User Name as John.
19. Select the View tab to preview the report.
20. In the Enter Parameter Values dialog box, select the parameter value drop-down list. You can see that only Canada is available for the user name.

    

21. Set the user name as David in the Options dialog box and preview the report again. This time, only the value United Kingdom is available in the parameter's value drop-down list.

• When applying an RLS policy to a parameter bound with a column, you must make sure the parameter's bound column and the column used to set conditions in the RLS policy are in the same table. In addition, if the RLS policy also contains conditions defined on other columns, all the columns must be in the same table, and the RLS policy cannot contain parameters and formulas; otherwise, when you apply the RLS to the parameter, the RLS would not work properly.
• When you have applied an RLS policy to a parameter and then you edit the SQL statement of the parameter via the Import SQL option in the parameter dialog box, the parameter value drop-down list may be Null because the changed SQL statement may not match the permissions of the RLS.
• When previewing a report that contains parameters applied with RLS in the Page Report Result or Web Report Result format in Designer, you need to make sure your RLS policy contains the user Jinfonet. That is because the user Jinfonet is the default and only user of the Preview Server. The Preview Server cannot recognize any other users in the RLS policy.

Supplementing WHERE Portions

You can change a query at runtime using the API method setWherePortion(). However, by calling this method, Logi Report Engine replaces the original WHERE portion of the query. If you want to append the runtime WHERE portion to the original one instead of replacing it, you can achieve it via the method in the following example without using the Java API.

1. Make sure SampleReports.cat is the currently open catalog file. If not, navigate to File > Open Catalog to open it from <install_root>\Demo\Reports\SampleReports.
2. In the Catalog Manager, expand the node of the data source where you want to add the parameter, then create a type-in parameter p_Portion of String type (leave the other settings to their default).
3. In the same data source, create a queryCustomersInfo on the table Customers. Select all the fields contained in the table.
4. Create a page report with a table in it based on the query, which displays the fields Customer ID, Customer Name, City, and Phone, and applies the Commercial style.
5. In the Data panel, right-click the node that represents the query, and then select Edit Query from the shortcut menu.
6. In the Query Editor dialog box, navigate to Menu > Query > Filter.
7. In the Search Condition dialog box, add two condition lines (WHERE portions) for the query. The colon in the second condition line is used to append the parameter value (of String type) to the first condition line instead of replacing it.

   

8. Select OK to apply the change to the query.
9. Select the View tab to preview the report.
10. In the Enter Parameter Values dialog box, write a WHERE portion in standard SQL syntax as value of p_Portion, for example, CUSTOMERID<20, then select OK. Designer applies both of the two WHERE portions to filter the query.

    

Previous Topic  Next Topic