Overview
This document is applicable to users who have installed the FineVis Data Visualization plugin to learn plugin functions.
Version
Report Server Version | FineVis Data Visualization Plugin Version | Functional Change |
---|---|---|
11.0.22 | V3.0.0 | / |
11.0.22 | V4.2.0 | FRM mobile App Re-layout and Component Order configuration supported conversion to FVS. For details, see section "Notes." |
Application Scenario
The Tool to Convert FRM Dashboards into Visual Dashboards can help you quickly convert FRM reports into FVS visualization dashboards.
Function Description
For the plugin version updated to V3.0.0 and later versions, a Conversion Tool Tab has been added to the directory.
Batch selection of FRM reports is supported for upload and batch conversion to FVS templates.
The selected/uploaded templates are displayed in a list format, supporting the display of FRM template names.
You can delete FRM templates from the uploaded list.
You can view the template conversion status.
Procedure
1. Log in to the decision-making platform, choose System Management > Conversion Tool, and click Upload to select the FRM reports that need conversion, as shown in the following figure.
2. Click Convert for conversion, as shown in the following figure.

1. You can delete the selected FRM templates.
2. The default Output Path is set to Original Template File Location, and you can switch the output path to Custom Directory.
3. After conversion is completed, a pop-up prompt saying "The template is converted successfully." is displayed, as well as the number of Successful Conversion and Conversion Failure.
Conversion Result is displayed on the right side of each template in the conversion list, as shown in the following figure.

Notes
1. When you use the conversion tool to process templates, certain functions are not supported for conversion or require manual adjustment. The following table describes specific content.
Function | Difference and Solution | |
---|---|---|
Widget |
| Difference FVS currently does not support data entry. Data entry widgets, for example, password widgets, are not available. Solution:
|
| Difference: FVS has been optimized based on application scenarios and usage frequency to simplify user understanding. Component triggers no longer distinguish between events before and after editing. Only the Edit End events are retained. Solution: The Edit End event can be used to replace the function. | |
Icon Color | Difference: The widget icon color adopts the theme color of the converted FVS template. Solution: You can set the icon color in FVS Template Style Management. | |
Tab Component |
| Difference: FVS has been optimized based on application scenarios and usage frequency. Tab components only support the tab switching events. Solution: If you need to configure interactions for components within a Tab, you can add click events to the corresponding components. After initialization events can be replaced by loading end events |
Tab Button Expansion Style on Mobile Terminals Up Menu Style, Down Menu Style, Sliding Style, and Row Style. | Difference: Tab component Style can be set to Sci-fi, Inline Style, and Underline in FVS dashboards. Solution: Manual adjustments are required with the Style and Position settings. | |
Mobile Dot Indicator | Difference: In FVS, the function has been changed and named to Navigation, without distinguishing between PC and mobile terminals. Solution: You need to manually tick the Enable Navigation button. | |
Padding and Interval settings in the Tab component on PC | Difference: Components in a Tab can be freely dragged and put with no need to set the padding and interval in FVS dashboards. Solution: You can drag the component to an appropriate position. | |
Mobile Terminal | Component Navigation | Difference: For FVS of versions before V3.1.0, this function is not supported. |
Refresh when the page is re-displayed | Difference: Due to product implementation differences, this function is not currently compatible with FVS dashboards. However, the specific use of the template remains unaffected. | |
Allow Double-click/Pinch to Zoom | Difference: Only the table components in FVS dashboards support this function. Future versions will gradually add support for this function. | |
Prompt Upon Leaving Without Data Submission | Difference: FVS dashboards do not support the Data Entry function currently. Future versions will gradually add support for this function. Solution: You are advised to embed a general report within the data entry page for creation. | |
Absolute Canvas |
| Difference: The absolute canvas is an empty container. FVS has been optimized based on application scenarios and usage frequency by removing the interaction event settings for the absolute canvas. Solution: Components in an absolute canvas can be configured. After initialization events can be replaced by loading end events |
Template Configuration | Widget Display Enhancement | Difference: The style settings corresponding to widget enhancements are largely covered in FVS dashboards. Solution: Manual adjustments are required. |
Opening Effect | Difference: The effect needs to be manually adjusted under Template Setting > Loading Effect in FVS dashboards. | |
Theme Style | Difference: Only styles already applied to components are supported for conversion. Solution: Manual configuration is required. | |
JavaScript Event | Difference: The calling APIs for FVS templates and FRM reports are different. Solution: You need to manually set the API to duchamp.xxx. | |
Chart Title | Difference: Differences exist in the chart title logic between FRM reports and FVS templates. Solution: You need to manually add the chart title. | |
Parameter Panel | Difference: The parameter panel will be automatically converted into a query panel in FVS templates, which will be displayed on the left side of the canvas. To achieve a similar effect of having the parameter panel at the top, you can simply add the corresponding widgets in the canvas. |
2. For the following scenarios, you are advised to continue using the FRM version or recreate the template in FVS dashboards.
Scenario | Suggestion |
---|---|
The data entry submission event is used. | The data entry section is created by using a CPT report and embedded into FVS as a pop-up window. |
Secondary development functions are used | You are advised to check whether FVS provides an alternative solution; if no alternative is available, you are advised to continue using the FRM template. |
Container nesting is used:
| Components within the container need to be copied and pasted into the FVS template. |
3. For FVS of version V4.2.0 and later versions, if you select App Relayout under Mobile Terminal > Mobile Attribute for an FRM template, Mobile Layout will be automatically selected for the FVS template converted from the FRM template.
The Component Order setting in Mobile Terminal will also be synchronized to the FVS template after conversion.
4. If the original FRM preview link has been used in a platform or another template, after converting the FRM report to an FVS template, you need to manually change the preview link suffix from frm to fvs to ensure normal access.