You are viewing FineBI 7.X help doc. You can click to jump to FineBI 6.X help doc.

BI/Spider Parameter

  • Last update:November 05, 2026
  • Overview

    Version

    FineBI Server Version
    Functional Change

    7.0

    /

    7.0.4

    Added the Max Personal Extraction Space (MB) configuration item under System Management > System Setting > BI Parameter.

    7.0.13

    Added the Standard Analysis Total and Expand/Collapse Row for Standard Analysis configuration items under System Management > System Setting > BI Parameter.

    Function Description

    FineBI allows you to configure and tune BI parameters in System Management, making it easier for admins and implementation personnel to quickly review current system configurations and apply settings directly on the page.

    You can log in to FineBI as an admin, then choose System Management > System Setting > BI Parameter to open the configuration page for BI and extraction parameters, as shown in the following figure.


    Basic Configuration

    Basic Function Configuration

    ParameterDefinitionDefault ValueWhether Project Restart Is Required After Modification

    Data Type Identification

    1. Decimal Place Handling Rule

    If the values of a field contain decimal places, the system always identifies the field’s type as numeric regardless of whether Data Type Recognition is enabled.

    2. Default Rule When Data Type Recognition Is Disabled

    • Digit count ≤ 15: When the digit count of values of a field is less than or equal to 15, the system automatically identifies the field’s type as numeric (integer or decimal).

    • Digit count > 15: When the digit count of values of a field is greater than 15, the system automatically identifies the field’s type as text (to prevent precision loss for large integers).

    3. Mandatory Rules When Data Type Recognition Is Enabled

    • All numeric fields are forcibly identified as numeric type (double).

    • Note: Since a double has an effective precision of 15 digits (2^52), precision loss may occur for numbers with more than 15 digits. Rebuild the data table after enabling this function.

    4. Tables Added While Data Type Recognition Was Disabled

    • Unedited tables: After you enable Data Type Recognition and restart the project, the field type automatically switches to numeric when you open the table editing page. Changes take effect upon saving.

    • Edited tables: After you enable the function and restart the project, the field remains the text type when you open the table editing page. Manual modification is required.

    Close

    Yes

    SQL Parameter and Filter Function  Effective for Widget

    Whether the widget binding SQL parameter function and filtering function take effect simultaneously

    Disabled

    No

    Chinese Sort

    Function description: sorting method selection

    • Disabled: Chinese sorting is disabled (default). All data is sorted by the UTF-8 code point order. Chinese characters in UTF-8 follow the Kangxi Dictionary sequence.

    • Enabled: Chinese sorting is enabled. Chinese characters in all data are sorted by pinyin.

    Modification Recommendation:

    FineBI V7.0.9 and later versions:   Make changes directly here.

    FineBI V7.0 to V7.0.8: Update the setting both here and in FineOps. After updating this setting under System Management > System Setting > BI Parameter > Basic Function Configuration in FineBI, log in to FineOps, choose Maintenance > Component Management, and modify the sorting setting for the bi-engine-worker and bi-engine-master components. For details, see Modifying Component Configuration. Ensure the sort setting for the bi-engine-worker and bi-engine-master components under Maintenance > Component Management in FineOps matches this Chinese Sort setting exactly:

    • If this function is disabled, set the component sort setting to bytes in FineOps.

    • If this function is enabled, set the component sort setting to pinyin in FineOps.

    Disabled

    Yes

    Smart Data Explanation

    Data Explanation Function Behavior Logic:

    • Disabled: Only custom-configured data explanation is triggered. System-default data interpretation is not triggered to prevent over‑utilization of data explanation.

    • Enabled: Both custom data explanation and system-default data explanation can be triggered.

    Note: This function depends on the licensed feature Data Interpretation.   Ensure this feature is licensed for the configuration to take effect.

    Disabled

    No

    Recordation of Polars Query Task's   Description

    Small PLS files are generated without performance degradation.

    Note: This setting is generally used only for troubleshooting assisted by our technical support. Do not enable it independently.

    Disabled


    Recordation of Polars Query Task's   Data

    Large SUITE files are generated, which will cause performance degradation.

    Note: This setting is generally used only for troubleshooting assisted by our technical support. Do not enable it independently.

    Disabled


    Recordation of BI Query Tasks

    BI query task descriptions are recorded.

    Note: This setting is generally used only for troubleshooting assisted by our technical support. Do not enable it independently.

    Disabled


    Spark Log Output Level

    Spark log output level for standard output stream; logs are written to Tomcat’s catalina.out file or FineBI’s nohup file.

    Available options: INFO, WARN, ERROR, and DEBUG

    • INFO: Error messages and basic execution logs are printed.

    • WARN: Warning or prompt information is printed.

    • ERROR: Only error logs are printed.

    • DEBUG: All logs are printed.

    INFO

    Yes

    Manual Preview Reminder (s)

    Unit: seconds

    Default value: The value is null by default, which means the manual preview parameter is disabled.

    After this parameter is configured, if the data query time for any component request exceeds the set duration, the system prompts you to enable manual preview without forcing it on. This reduces query pressure on the engine.

    The setting takes effect immediately. No project restart is required.

    Null

    No

    Standard Analysis Total

    When the function is enabled, Total Summary Row will be checked by default for group tables and cross tables in standard analysis subjects. This may slightly affect the paginated query performance of components.

    Disabled

    No

    Expand/Collapse Row for Standard   Analysis

    When the function is enabled, Expand/Collapse Row will be checked by default for group tables and cross tables in standard analysis subjects, and the tables will be displayed collapsed by default. This may slightly affect the initial query performance of components.

    Disabled

    No

    Data Update Configuration

    ParameterDefinitionDefault ValueWhether Project Restart Is Required After Modification

    Default Update Settings for   Self-service Dataset

    Whether the self-service dataset single table updates with the parent table

    For details, see Single Table Update of Self-Service Datasets.

    Update With Parent Table

    Yes

    Update High Performance Interval

    There is no limit on resource pool core consumption during the configured period.

    To avoid disrupting user operations, you are advised to set this to a period when the system is idle, and update tasks run frequently.

    Null

    Yes

    Active Period of Accessed Dataset   (Day)

    Dataset active period after access

    A dataset is considered active if either of the following conditions is met:

    • Dashboards or components built from the dataset are edited or accessed within X days.

    • A child table of the dataset is an active table.

    Unit: day

    14

    Yes

    Active Period of Created Dataset (Day)

    Dataset active period after creation

    A dataset is considered active within X days of its creation and inactive beyond that.

    Unit: day

    7

    Yes

    Global Check Time of Dataset Activity

    Check time for dataset active status evaluation

    Dataset access and creation records are checked collectively at this time to refresh active status. Some datasets will then be marked as non‑extracted.

    Available options:

    Check at Fixed Time: The dataset active status is checked daily at hh:mm:ss.

    Check Before Global Update Schedule Task

    Check at Fixed Time

    00:00:00

    Yes

    Restriction Parameter

    Data Access Restriction

    ParameterDefinitionDefault ValueWhether Project Restart Is Required After Modification

    Data Access Volume

    The data access volume limits the number of data rows that can be read into the server memory. Not all computing scenarios with large data volume load all data into memory. The FineBI Spider engine applies intelligent memory usage strategies, such as:

    • If the number of data rows after group summary exceeds the configured value, computations in components or dashboards will be aborted.

    • For the smaller of the two tables involved in a horizontal merge, if the row count after grouping by the join field exceeds the configured threshold, calculations in the component or dashboard will be interrupted.

    A low configuration affects the accuracy of data calculations.

    High configuration may lead to system downtime.

    Unit: row

    Configurable range: from 0 to 10,000,000

    Recommended configuration range: from 10,000 to 1,000,000. Keeping the default value is recommended.

    1000000

    Yes

    Data Volume During Subject Edit

    The volume of data processed in real time during data edit at each subject level is limited (default volume: 10,000,000). This parameter can take effect without restarting the server.

    Configurable range: from 100,000 to 10,000,000

    If you need to adjust the upper limit, you can contact technical support to modify the configuration file in FineDB.

    10000000

    No

    Analysis Subject Query Calculation Restriction

    Parameter
    DefinitionDefault ValueWhether Project Restart Is Required After Modification

    Direct Connection Query Timeout (s)

    Long component query time caused by too many components, and the blocked BI request caused by long query time for a component may be mistaken as downtime.

    To solve the problem, you can set a direct query timeout. All real-time data queries will be interrupted when they time out, in case slow queries block normal queries.

    Error will occur: Component query time exceeds {} minutes; query is interrupted.

    Unit: seconds

    Recommended configurable range: from 10 to 300

    Effect scope: BI direct query requests for anything except table structure

    180

    No

    Number of Direct-Connection Lineage Levels

    The maximum lineage level of the direct-connected dataset is limited to prevent the generated SQL statement from being too complex and affecting the dashboard loading speed.

    Configurable range: from 2 to 6

    If you need to adjust the upper limit, you can contact technical support to modify the configuration file in FineDB.

    3

    No

    Number of Complex Calculation Steps in Direct-Connected Self-Service Dataset

    The maximum number of complex calculation steps in the direct-connected self-service dataset is limited to prevent the generated SQL statement from being too complex and consuming a large amount of memory and CPU during calculation.

    The complex calculation steps include joining tables, adding columns from other tables, adding summary columns, converting rows to columns, and converting columns to rows.

    Configurable range: from 0 to 6

    If you need to adjust the upper limit, you can contact technical support to modify the configuration file in FineDB.

    2

    No

    Extraction Query Timeout (s)

    Long component query time caused by too many components, and the blocked BI request caused by long query time for a component may be mistaken as downtime.

    To solve the problem, you can set the extraction query timeout. All extracted data queries will be terminated after the timeout to prevent abnormally slow queries from blocking other normal queries.

    An error may occur: Component query time exceeds {} minutes; query is interrupted.

    Unit: second

    Recommended configurable range: from 10 to 300

    45

    No

    Number of Extraction Lineage Levels

    The upper quantity limit of extraction dataset lineage levels is limited to prevent the generated SQL statements from being too complex and the dashboard loading speed from being affected.

    Configurable range: from 1 to 10

    If you need to adjust the upper limit, you can contact technical support to modify the configuration file in FineDB.

    16

    No

    Number of Nested Levels in DEF Formula

    The maximum nested levels of the DEF function in the formula is limited to prevent the generated SQL statement from being too complex and the calculation from taking too long (affecting the dashboard loading speed). This parameter can take effect without restarting the server.

    Configurable range: from 0 to 4

    If you need to adjust the upper limit, you can contact technical support to modify the configuration file in FineDB.

    4

    No

    Number of Calculation Fields Added to Component

    The maximum number of calculation fields that can be added to a single component's analysis area is limited to prevent the parsing performance of multiple formulas from being affected.

    No limit

    No

    Number of Components in Dashboard

    The maximum number of components in a single dashboard is limited to prevent high database query concurrency due to excessive SQL queries delivered during single-dashboard access.

    No limit

    No

    Max Memory Per Engine Query Task

    Unit: bytes

    The parameter is used to limit the memory consumed by a single engine query task to prevent outages caused by excessive memory consumption from one individual task.

    This parameter can take effect without a restart.

    2147483648

    No

    Data Update Restriction

    ParameterDefinitionDefault ValueWhether Project Restart Is Required After Modification

    Scheduled Update Frequency (Minute)

    The scheduled update frequency set for a single dataset is limited to prevent excessive system load caused by a high update frequency of business settings.

    Unit: minute

    No limit

    No

    Number of Cells in Extracted Self-Service Dataset

    The number of cells in the final result of the extracted self-service dataset is limited to avoid excessive disk space usage and slow extraction updates.

    No limit

    No

    Max Personal Extraction Space (MB)

    This parameter specifies the maximum space (unit: MB) that can be occupied by data extracted by users (excluding super administrators) in My Analysis to prevent a user from occupying too much disk space without a restraint.

    Unit: MB

    Whitelist Configuration Description:

    • You can search for usernames of all platform users except super administrators (excluding deleted users), and configure different extraction space limits.

    For example, most employees in a company are allocated an extraction space quota of 100 MB, while some senior analysts are allocated 1 GB. Enter 100 on the general parameter configuration page, and enter 1024 in the whitelist configuration.

    • Maximum whitelist entry: 100

    • If a user added to the whitelist is deleted on the platform, the whitelist entry remains valid.

    Capacity Management:

    You can click Capacity Management to view user usage and relevant information:

     

    Display Entry for Individual Users:

    You can choose My Analysis > Data Space Capacity to view the capacity information.

     

    Note: For FineBI of versions earlier than 7.0.4, there is no default limit for users. The previously configured upper limit parameter (userExtractDataSpaceLimit)  is supported for backward compatibility.

    1000 MB


     
     

    For legacy users on FineBI of versions earlier than 7.0.4, the default value is empty (no limit).

    No

    Resource Export Restriction

    Parameter
    DefinitionDefault ValueWhether Project Restart Is Required After Modification

    Data Volume Limit on Excel Export

    Data volume limit during Excel export. If this limit is exceeded, an error will be reported directly.

    Unit: cell (No. of row * column)

    Configurable range: from 0 to 2,000,000,000

    Recommended configurable range: from 0 to 1,000,000,000

    Null

    No

    Available Disk Space Upon Excel Export  (GB)

    When exporting Excel files, a disk space check is performed, and the export behavior will be interrupted when the disk space is less than the limit value. This can avoid downtime caused by a full disk.

    If the limit is triggered, errors will occur: The current exported data volume is too large, and there is not enough disk space. The system protection mechanism has been triggered, and the export is interrupted. Clear the disk space in time, limited by the Excel Export Disk Space Check parameter; disk space limit:{R1} GB.

    Configurable range: from 5 to unlimited

    5

    No

    Concurrent Thread Quantity Limit Upon   Detail Table Export

    When multiple users export Excel files with a large data volume at the same time, the number of users may exceed the number of threads and affect the user experience. Therefore, you can use the parameter to set the number of users. If this limit is exceeded, business personnel have to wait.

    Configurable range: from 1 to 10

    Recommended configurable range: from 1 to 5. (You are advised to keep the default value.)

    3

    Yes

    Data Cache

    For details, see BI Cache.

    附件列表


    主题: System Management
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy