6.1.3
2024-10-23
By using the Format Painter tool, you can quickly apply the style of one component to other components for style consistency and aesthetics, improving the style adjustment efficiency.
For details, see Component Format Painter.
You can determine by yourself whether to allow condition attributes to take effect for the summary row.
If Take Effect for Summary Data is selected, the set condition will take effect for the summary row.
If Take Effect for Summary Data is not selected, the set condition will not take effect for the summary row.
For example, rank Total Amount by choosing Quick Calculation > Ranking, and set the background color of the cell containing the top 1 amount to red, as shown in the following figure.
For details, see Table Property.
You can set the value format for the fields multi-selected by pressing Ctrl, improving the value format adjustment efficiency.
For example, set Quantity Unit in Value Format to Thousand for Sale Volume and Gross Profit.
For details, see Value Format in a Table.
Word Cloud
1. Colors cannot be differentiated through Graphic Property.
2. Invalid legends are displayed, causing chart messes.
1. Colors are differentiated based on the first dimension dragged into Color in Graphic Property.
2. Invalid legends are removed.
Area Chart
1. Line type: polyline
2. Effect: off
3. Legend: slightly thin
1. Line type: curve
2. Effect: on
3. Legend: bold
Gauge
Style: standard
Style: simple
Components are displayed from left to right and from top to bottom based on their physical positions on PC.
Components contain filter components, floating/combined components, and other components (including frozen bars of filter components), which are taken into consideration together for position coordinate calculation.
When you manually replace JAR packages for minor version upgrade of FineBI deployed on non-O&M platforms, human factors may cause upgrade failure and even startup failure due to project downtime.
FanRuan provides BI Version Management Tool for minor version upgrade of FineBI deployed on non-O&M platforms.
For details, see How to Upgrade Non-Containerized FineBI Within 6.0.x (Minor Versions).
To facilitate customers' understanding and communication, the names of function points in Registration Management are consistent with those in the FanRuan quotation.
For details, see Registration Management.
In 6.1.3 and later versions, if you select the sub-department as the data alert receiver, only users from the sub-department can receive the notifications. Users from sub-departments to which no management permission is assigned and users directly from the parent department cannot receive the notifications.
For the data alert tasks created before the upgrade, the new receiver logic will not take effect automatically after the upgrade, but can take effect after you click the edit and saving buttons on the data alert page.
When scheduled tasks in BI have high concurrency, task execution may be delayed.
You can use the FINE_CONF_ENTITY Visualization Configuration plugin to adjust the number of threads executing scheduled tasks in BI to avoid the above problem.
Adjust this parameter carefully, as a high number of threads may result in poor project performance and affect normal use by business users.
For details, see Task Schedule FAQ.
If you do not want to execute scheduled tasks for a specified node in a multi-node cluster project so that business resources can be sufficient, you can add -Dschedule.disable=true. (Dschedule.disable is the project node startup parameter.)
For the project node with this parameter set to true, scheduled tasks will not be executed, and only manually-triggered tasks will be executed.
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy