反馈已提交
网络繁忙
FineBI Version
JAR Package Version
6.0.9
2023/04/25
Direct data can match with GBase8t data connection.
Direct data can match with Informix data connection.
To save update resources, if a user does not use a data table for a long time, the table will not get updated. Click this table, it will prompt The Data is not active and will not be extracted temporarily.
To use this table, click Update Information > Update now.
For details, see Self-service Dataset Single Table Update.
If users want to check the component or dashboard based on the inactive table, it will prompt: The data is not active, and the activation will be triggered automatically after waiting for 5s.
That is, the table will be automatically updated and users can view the data in 5 seconds.
The admin can set the parameter to define a data table as active.
For details, see BI/Spider Parameter.
Spider dataset supports editing and adding data again. For details, see Spider Dataset Plugin.
Added Data detail to help users learn about the information of tables in Public Data.
Click Data detail to learn about the creator and last update time of a public dataset in Public Data.
When users have questions about the data, they can quickly find the creator of the data table for confirmation.
Added Field description.
After successfully setting the field description, users can see their notes when they hover over the field name while using the data table. For details, see Data Preview.
Support dragging Excel files from folders or desktop in Select Data interface.
If the uploaded Excel file has multiple sheets, the file name corresponds to the sheet name respectively by default.
FineBI 6.0.8 added model function for analysis subjects. There is only one model for each subject. The model corresponds to all the data and components within the subject.
To-Be-Analyzed Area
All components' configurations of to-be-analyzed area within the subject will be copied to the subject model. You can reuse multiple tables associated with the table/model to create other components, improving production efficiency.
For example, use table A to create component 1. Meanwhile, you have made settings like copying fields, adding detail filter and parameters, and so on in to-be-analyzed area.
When you use table A to create Component 2, these settings will still be retained.
After you upgrade FineBI, the components' configurations in to-be-analyzed area in the subject will be copied to the upgraded subject, and the same configuration will be compatible. Compatibility details are shown below:
Note:
1. Only components made from the same table in the model will have their fields merged.
2. The configuration items copied and integrated into the subject will be synchronized to all components.
Component Configuration for To-Be-Analyzed Area
Compatibility Description
Drilling directory
Premise: There are multiple components using the same table made within the current subject. (Component 1 and Component 2 both use table 1.)
1. If the drilling directory in to-be-analyzed area are exactly the same, then the drilling directory will be integrated and preserved.
Drilling directory of Component 1: a > b > c
Drilling directory of component 2: a > b > c
One directory after upgrade: a-b-c
2. If the drilling directories are not completely identical, copy the fields used in these drilling directories, integrate, and retain them.
Drilling directory of Component 2: a > b > d
Two drilling directories after the upgrade: a > b > c and a-1 > b-1 > d
3. Components with the same field do not always in the drilling directory simultaneously. If it is the first drilling field, it will be copied. If it is not the first field, only one field can be retained.
Component 2 has no drilling directory.
The drilling directory after upgrade: a > b > c Copied field: a-1
Copied field
1. Copy and integrate the fields of multiple components in to-be-analyzed area into the subject.
2. Only one field will be retained if the following conditions are met: the copied field name and the configured one are exactly the same.
Calculation field
2. Only one field will be retained if they are completely identical.
Parameter
Copy and integrate the fields of multiple components in to-be-analyzed area into the model.
Only one field will be retained if the following conditions are met:
Parameter type and parameter name are the same, and no filtering component is bound.
The parameter type and parameter name are the same. The bound filtering component is the same.
Convert Dimensions to Indicators
Convert Indicators to Dimensions
Same as rules of calculation field
Geographical role - Indicators
Geographical role - Dimensions
Detail filter
The filter conditions are exactly the same.
The parameter needs to meet certain conditions if there is a parameter bound to filter component in detail filter: The parameter type and name are the same. The parameter is bound by the same filter component.
Record numbers
Create component 1 with records by using table 1 and set condition A in detail filter.
Create component 2 with records by using table 1 and set condition B in detail filter.
All records will be retained after upgrade. The result is record number and record number-1.
Indicator name
Reserved
Analysis Area
Filed compatibility does not influence the fields added in analysis area.
Note: If you use drilling directory to create components, when the non-first directory fields in the drilling directory are not set with display names in the analysis area, the drilling directory fields in the analysis area may appear as field names such as {name}-1, {name}-2.
IN function is used to determine whether the result of the expression belongs to the set constructed by parameter 1, parameter 2, parameter 3, ..., and parameter N. If the result of the expression belongs to the set, the return value is 1. Otherwise, it is 0.
For example, calculate the contract amount of permanent orders in Contract table.
To determine whether the contract type is Permanent, use the formula IN(contract type,"permanent").
To calculate the contract amount of the permanent orders, use the formula DEF_ADD(SUM_AGG(contract amount),[],IN(contract type,"permanent")).
NOT function is used to judge whether the expression belongs to a certain condition. If the expression belongs to the condition, the return value is 0. Otherwise, the return value is 1.
For example, calculate the contract amount of orders that are not Permanent.
Enter the formula DEF_ADD(SUM_AGG(Contract Amount),[],NOT(IN(Contract Type,"permanent"))).
The icon of published data/dashboard is optimized.
You can group and move analysis steps.
Press Ctrl and Shift keys at the same time to select multiple steps, click Create group, and group selected steps into one group.
If you need to modify the order of steps, you can directly move by dragging.
If you have quoted parameters to filter, the details of the parameter filter will be displayed.
For details, see Viewing Component Filter Condition.
Application Scenarios
There is one model in one analysis subject. The model includes all the tables in the subject. It supports sync operations on all the tables.
The subject model can meet users' analysis needs in multiple dimensions. Users can set associations among different tables in the model to make a cross-table analysis within a single subject.
Scenario 1: Simplified Data Preparation Process
The model can quickly associate multiple tables and combine them into one large table for analysis without updates. It allows users to directly add fields in the component to immediately make analysis.
Scenario 2: Easier Component Analysis Reuse
The operations in the pending analysis area, including adding calculation fields, drilling down, and detail filtering, will be synchronized to the model. Users can directly use the fields in this table without copying components.
Scenario 3: Directly Using Multiple Table Fields Under Associated Tables for Calculation
Cross-table fields can be directly added to calculation fields for analysis.
Scenario 4: N:N Association Scenarios
Components created with associated tables can be linked to each other for users to view filtered results.
Functions
In data editing interface, click to switch to model view. Users can set the model relationships among different tables by dragging.
Also support configuring the associations between tables.
Tables associated in the model will be merged into the pending analysis area for component analysis. Cross-table analysis is supported.
For example, calculate profit in the component to analyze the profit of different products.
Add the component 1, then the profit calculated in the component can be synchronized to the component 1. There is no need to copy components any more. This can reduce operation steps and improve field reuse efficiency.
For details, see Pending Analysis Area Setting Introduction.
For details about update compatibility, see section "Compatibility Introduction".
Optimized the entry for adding calculation fields. Click ... in the upper right corner to add calculation fields.
The dimension and indicator bar have been removed. The fields are now grouped by table name.
All fields within a table can be expanded or collapsed.
Support filtering all the tables within the subject in the pending analysis area.
Tables that are associated within the subject model will be merged and displayed together.
After the model establishment, the associated multiple table fields can be combined and analyzed randomly within the component.
For details, see Subject Model Example.
For example, calculate the sales quantity of different products in Tokyo with the calculation fields in the tables that have been associated in the subject model.
The field The Sales Quantity of Different Products in Tokyo belongs to the Cross-table fields. Drag Name, The Sales Quantity of Different Products in Tokyo, and Quantity to the field analysis area so as to compare the sales quantities between Tokyo and other cities.
Note: The indicator name also belongs to the Cross-table fields.
In the process of cross-table analysis, fields are from different tables. When hovering over a field, users can view the source table of the field.
To ensure smooth usage, it is recommended to add all tables for analysis to the subject beforehand. As for existing users, the update will not affect the existing data. As for new users, version 6.0.8 or later will not have this feature.
Support selecting fields in the associated tables in the dashboard analysis (filtering, linkage, and drilling). This will make analysis more flexible and diverse.
For example, in the filtering component, Used fields on the left side of the interface refers to the fields added to the component. All Fields displays the fields within the source table of the component or the fields within the associated tables.
For details, see Basic Functions of Filter Components.
To sort the filtering fields, users can use the fields in the associated tables as the basis for sorting.
Drop-Down Tree Filter Component also supports adding fields in the associated tables.
Filter Component supports filtering calculation fields according to the needs of users for more application scenarios.
If a component is created with the fields in the associated tables, it will display the update information of different source tables.
Added the limits for unreasonable calculations. If the data volume is too huge after Group Summary or Left and right merge, the calculation in components/dashboards will be interrupted.
You can modify the data volume of charts in big data mode. If you do not want to use the big data mode, which may result in incomplete display of data, you can adjust the parameter values.
Manage logs can record information about data links, map configurations, public data, publishing management, and the recycle bin.
You can configure the absolute path of extract data storage through node files in extract clustered environment.
Disabled data synchronization for asynchronous nodes at the configuration level to ensure that no data exists on asynchronous nodes.
For details, see Extract Cluster.
feedback
鼠标选中内容，快速反馈问题
鼠标选中存在疑惑的内容，即可快速反馈问题，我们将会跟进处理。
不再提示
10s后关闭