Dynamic Cell Attributes - Filtering

Overview

Use Cases

In Chinese-style Reporting Pro Cards, filtering mainly addresses two core scenarios: detail filtering and multi-View analysis.

• Detail filtering: view data details under specific conditions in the report, for example filtering records where Sales Region = East China or where sales amount is greater than 100.
• Multi-View analysis: use information from one View, such as View 1, to inspect related data in another View, such as View 2. For example, use Region values from View 1 to inspect spending amounts in View 2, with Product Type as the relationship key.

Feature Overview

Except for virtual Views, all fields dragged from regular Views in the format {{view.fieldName}} or {{=aggregationFunction(view.fieldName)}} support filtering.

Filtering is a type of dynamic cell attribute, abbreviated as the F attribute. Right-click and select Dynamic Attributes, or double-click a template cell to open the configuration panel and configure filtering. Four types are supported: Selection, Range, Condition, and Field.

The filtering types are described below:

Type	Use Case and Description	Example	Supported Field Types
Selection	Used for detail filtering scenarios. Enumerates all values in the field so users can select the needed values. Supports manual selection and batch paste.	For example, select East China, Central China, and North China as Regions, and view sales amounts only for the selected regions.	Text, Date
Range	Used for detail filtering scenarios. Supports operators such as >, <, ≥, ≤, =, and ≠.	For example, filter data after January 1 of the current year.	Date, Number
Condition	Used for detail filtering scenarios. Supports operators such as =, ≠, Contains, Does Not Contain, Starts With, Ends With, Does Not Start With, and Does Not End With.	For example, filter records where Product Category contains “Food”.	Text
Field	Used for multi-View analysis scenarios.	For example, if you have a Sales Target View and a Sales Performance View, you can use Region and Product Category from the Sales Target View as dimensions to view actual sales quantity from the Sales Performance View. Set filtering on cell D2 with Region = field = Sales Target View.Region and Product Category = field = Sales Target View.Product Category, and set the parent cell of D2 to B2.	Date, Text, Number

Steps

In the following example, the goal is to analyze the sales performance of different product categories under different Regions. The Sales Target table and Sales Performance table are two separate Views, so filtering is needed for cross-View analysis.

1. Create a Chinese-style Reporting Pro Card, enter the data preparation stage, add the Views to be analyzed, then click Save and Continue to enter the template editing page.

2. Edit the header and drag the required fields from different Views into the corresponding cells, as shown in the example below. The Views used are the Sales Target table and the Sales Performance table.

   

3. Configure filtering attributes as needed. See Feature Overview for the detailed explanation of each filtering type.

   Note

   Except for virtual Views, all fields dragged from regular Views in the format {{view.fieldName}} or {{=aggregationFunction(view.fieldName)}} support filtering.

   • Configure filtering for A2: only East China, Central China, and North China should be displayed as sales regions, so configure the filtering attribute of cell A2 as shown below.

     

   • Configure filtering for D2: use Region and Product Category from the Sales Target View as dimensions to view the actual sales quantity in the Sales Performance View. Configure the filtering attribute of D2 and set its parent cell to B2.

     

   • Configure filtering for E2: use Region from the Sales Target View as the dimension to view the total actual sales quantity of the corresponding Region in the Sales Performance View. Configure the filtering attribute of E2, and since the sales quantity needs to expand by sales region, set the parent cell of E2 to A2.

     

   The filtering and parent-cell settings of D2 and E2 show that filtering only establishes the relationship between the two Views. Expansion still relies on Parent Context. In some scenarios, adjacent parent cells already have a default parent-child relationship, in which case the default parent cell can be used.

4. Preview the filtering result.

   

Notes

The filtering capability was upgraded in version 7.1. To ensure a smooth transition during upgrades or migration to the new filtering logic, the following compatibility strategies are provided:

• Compatibility for historical templates: templates that already use filtering and whose filtering configuration has not been modified continue to work normally with the old filtering logic.
• Filtering logic for re-edited templates: if a template's filtering configuration is edited again, saving the filtering configuration applies the new filtering logic and prompts the user to update the filtering conditions.
• Handling templates that contain both old and new filtering logic: if both old and new filtering logic exist in the same template, for example when new filtering is added to a historical template, all filtering must follow the new filtering logic. A prompt appears during save or preview, and the user must update the filtering configuration according to the new rules.

Note

Filtering null values is not supported at this time.

For differences between the old and new filtering capabilities, see Product Behavior Change Notes.