This document introduces the compatibility and notes for updates in different minor versions of FineBI 6.0 in detail.
The JAR package on which FineDataLink of the 4.1 version depends is embedded in FineBI of 6.0.17 and later versions.
FineBI with FineDataLink not integrated
1. Update FineBI by referring to How to Upgrade FineBI Between Minor Versions.
2. After the update, the product is embedded with the FineDataLink 4.1 module. If the originally-registered license does not contain FineDataLink-related function points, the FineDataLink functions will be displayed as unregistered. If you need to use these functions, contact our sales to purchase them.
FineBI with FineDataLink 4.1 integrated
1. Manually delete the fdl-xxx.jar package from the %Tomcat_HOME%/webapps/webroot/WEB-INF/lib directory.
2. Update FineBI by referring to How to Upgrade FineBI Between Minor Versions.
3. After update, the product is embedded with the FineDataLink 4.1 module and can be used normally.
FineBI with FineDataLink 4.0 integrated
Notes
1. The FineDataLink of the 4.0 version cannot be retained and must be upgraded to the 4.1 version.
2. Function points registered in the FineDataLink 4.1 version are not compatible with those in the 4.0 version.
If you no longer use the FineDataLink functions after the upgrade, re-registration is not required.
If you need to use the FineDataLink functions after the upgrade, you need to regenerate the license for registration. Contact our business personnel about this in advance.
Upgrade Procedure
3. According to the business guidance, perform re-registration.
FineBI For Excel
After updating FineBI to the 6.0.17 version, you need to update the FineBI For Excel plugin to the 7.0.16 version.
Paying users can contact our technical support (through the email address international@fanruan.com or the xxx icon) to obtain the plugin with the corresponding version.
Compatibility Description
You are advised to manually replace the class file in the server dataset when updating FineBI from 6.0.15 or earlier versions to 6.0.16 or later versions.
After this replacement, you can configure datasets through the latest BI system without needing to manually replace the class file in subsequent updates.
Procedure
Download 6016+.zip and decompress the file.
Cover and update the file to the path %BI_HOME%/webroot/WEB-INF/classes/com/fr/log.
After updating FineBI to the 6.0.16 version, you need to update the FineBI For Excel plugin to the 7.0.15 version.
Paying users can contact our technical support (through the email address international@fanruan.com or the icon) to obtain the plugin with the corresponding version.
Note: After updating the plugin, you need to restart the FineBI project for the changes to take effect.
You need to manually replace the class file in the server dataset when updating FineBI from 6.0.14 or earlier versions to 6.0.15 or later versions. After the replacement, you can configure datasets through the latest BI system.
Download 6015class.zip and decompress the file.
HTML5 Mobile Display
After updating FineBI to the 6.0.15 version, you need to update the HTML5 Mobile Display plugin to the 11.0.88 version.
Otherwise, component groups in dashboards cannot be effectively displayed on mobile terminals.
After updating FineBI to the 6.0.15 version, you need to update the FineBI For Excel plugin to the 7.0.14 version.
Note:After updating the plugin, you need to restart the FineBI project for the changes to take effect.
You need to manually replace the class file in the server dataset when updating FineBI from 6.0.13 or earlier versions to 6.0.14 or later versions. After the replacement, you can configure datasets through the latest BI system.
Download 6013+.zip and decompress the file.
BI Detail Table Export as CSV
After updating FineBI to the 6.0.14 version, you need to update the BI Detail Table Export as CSV plugin to the latest version.
To update FineBI integrated with FineDataLink to the 6.0.13 version, you need to update FineDataLink to the 4.0.28.1 version.
Paying users can contact our technical support (through the email address international@fanruan.com or the icon) to obtain the JAR package with the corresponding version.
In historical versions, all dimensions in the current view are automatically calculated for summary. But if rows are collapsed, the calculation result will be summed again.
In FineBI 6.0.13, only the concatenated dimensions used by the current summary view are automatically calculated for summary.
You need to manually replace the class file in the server dataset when updating FineBI from 6.0.12 or earlier versions to 6.0.13. After the replacement, you can configure datasets through the latest BI system.
Download 2023.08.30-6013+.zip and decompress the file.
After updating FineBI to the 6.0.15 version, you need to update the FineBI For Excel plugin to the 7.0.13 version.
No JAR packages on which FineDataLink-related functions depend are embedded in FineBI of 6.0.12 and later versions.
Fresh Installation
FineDataLink-related functions are no longer embedded in FineBI.
To integratedly use FineDataLink, contact technical support to obtain the relevant JAR package of FineDataLink.
Low-Version Update
For projects that integratedly use FineBI and FineDataLink functions in FineBI of 6.0.11 and earlier versions:
To update FineBI to 6.0.12 or later versions, you need to update the relevant JAR packages of FineBI and FineDataLink for proper use.
You need to contact technical support and demand the latest JAR packages of FineBI and FineDataLink.
In FineBI 6.0.12 and later versions, the lineage level for data tables can at most be 16.
To-be-created data tables cannot exceed the maximum level limit.
For historically created data tables that exceed the limit, you can still use them to create components and dashboards, but cannot use them to create sub-tables with deeper levels.
In this case, you are advised to optimize the lineage level of the parent table.
You need to manually replace the class file in the server dataset when updating FineBI from 6.0.11 or earlier versions to 6.0.12. After the replacement, you can configure datasets through the latest BI system.
Download log-2023.07.06.zip and decompress the file.
After updating FineBI to the 6.0.12 version, you need to update the HTML5 Mobile Display plugin to the 11.0.83 version.
FineBI 6.0.11 blocks the copy and paste function in historical steps of self-service datasets.
The next version of FineBI will fix relevant problems and reopen the function entrance.
FineBI 6.0.11 allows you to solve the problem of slow startup for the cluster.
The admin can manually delete the bitmap file in the spark cache of the temp directory and restart the project.
If FineBI with integrated FineDataLink is deployed in WebLogic, an error will appear when you (as common users) log in to the project.
If you do not use the FineDataLink, manually delete the fdl-xxx.jar package from the %Tomcat_HOME%/webapps/webroot/WEB-INF/lib directory.
If you use FineDataLink, postpone the update and directly update FineBI to the 6.0.17 version.
Problem
Since the parameter security verification is added in FineBI 6.0.10, the cbb JAR package is modified. After updates of some projects, the JAR package in the WebLogic container used by the project conflicts with the modification.
In this case, the project may fail to be started or some functions may be unavailable. The relevant error keyword validation or validator appears in the project log.
Solution One
1. Locate the weblogic.xml file in the /webroot/WEB-INF directory. If the file does not exist, create it.
2. Configure filtering in the weblogic.xml file and prioritize the use of the JAR package embedded in the application.
3. After saving the file, restart the project for the changes to take effect.
Download and decompress weblogic.zip.
Solution Two
1. Download javax.validation.jar.
2. Upload the downloaded file in the /weblogic/Oracle/Middleware/oracle common/modules directory to overwrite the lower version of the javax.validation.jar file.
Since the parameter security verification is added in 11.0.16, the cbb JAR package is modified. After updates of some projects, the JAR package in the WebSphere container used by the project conflicts with the modification.
Solution:
1. Download javax.j2ee.validation.jar.
2. Upload the downloaded file in the %WebSphereHome%/AppServer/plugins directory to overwrite the lower version of the javax.j2ee.validation.jar file.
/
The model function is added for analysis subjects in FineBI 6.0.8. One model only corresponds to one subject. The model corresponds to all data and components in the subject.
Configurations in the to-be-analyzed area for all components in the analysis subject are copied and pasted to the subject model. You can reuse other components created through the current table or multiple tables associated with the model to improve efficiency.
Configurations in the to-be-analyzed area for components created through the same table in the analysis subject are copied and pasted to the subject. Same configurations are compatible. The following table describes the compatibility in detail.
1. Only fields in components created through the same table in the model can be merged.
2. Fields added in the analysis area will not be affected by the field compatibility. If you create components through the drilled directory and do not set the display name in the analysis area for the non-first directory field in the drilled directory, the field name may be displayed as XX-1 and XX-2 in the analysis area.
Drilled Directory
Premise: Multiple components are created through the same table in the current subject. (That is, Component 1 and Component 2 are both created through the table 1.)
1. If the drilled directory in the to-be-analyzed area is exactly the same, the drilled directory will be integrated and retained.
For example, the drilled directory of Component 1 and Component 2 is a > b > c.
The drilled directory after update is a > b > c.
2. If the drilled directories are not completely identical, fields to be used by the drilled directories will be copied and the directories will be integrated and retained.
For example, if the drilled directory of Component 1 is a > b > c and the drilled directory of Component 2 is a > b > d.
The drilled directories after update are a > b > c and a-1 > b-1 > d.
3. If components with the same field do not always in the drilled directory simultaneously, the first drilled field will be copied and other fields will be retained only one.
For example, the drilled directory of Component 1 is a > b > c and no drilled directory exists in Component 2.
The drilled directory after update is a > b > c and the field a-1 is copied.
Copied Field
1. Fields of multiple components in the to-be-analyzed area are copied and pasted and integrated into the subject.
2. Only one field will be retained if the condition that the name of the copied field is the exactly same as that of the configuration is met.
Calculation Field
2. Only one field will be retained if fields are completely identical.
Parameter
1. Fields of multiple components in the to-be-analyzed area are copied and pasted and integrated to the model.
2. Only one field will be retained if the following conditions are met: The type and name of the parameter are the same and no filtering components are bound.
The parameter type and parameter name are the same and the bound filtering components are the same.
Converting Dimensions to Indicators
Converting Indicators to Dimensions
The rules are the same as those in Calculation Field.
Geographical Role - Indicator
Geographical Role - Dimension
Detail Filtering
1. Fields of multiple components in the to-be-analyzed area are copied and pasted and integrated into the model.
2. Only one field will be retained if the following conditions are met:
The filtering conditions are exactly the same.
If the parameter bound to the filtering component is added in the detail filtering condition, the parameter type and name should be the same and the parameter should be bound by the same filtering component.
Count
2. If Component 1 with Count is created through table 1 and the detail filtering condition A is set, and Component 2 with Count is created through table 1 and the detail filtering condition B is set, Count in these two components will both be retained. The result is Count and Count-1.
Indicator Name
The indicator name is retained.
You can refer to the document FineBI 6.0 Compatibility Instruction.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy