6.0.4
-
6.0.5
Added Data Used Space and Affected Users to Public Data Management.
Optimized Public Data Management to allow sub-admins to use.
6.0.10
1. Optimized the content of public data detection.
Views in Last 30 Days was changed into Recent Views.
Merged Creation Time and Publication Time into Creation/Publication Time.
Added Last Use Time of Other Users and Update Mode.
Deleted Engine Type, Dept and Position of Creator, Creator Role, Last Use Time, and Last Edit Time.
2. Added Detect Views in Last: N Days, which allows customizing the detection date.
3. Optimized Export Excel to allow exporting public data detection results as an Excel file.
6.0.12
Added Lineage Level to the content of public data detection and the search panel.
6.1.5
1. Added User Data Management to help you manage the data in My Analysis.
2. Merged the former Public Data Management and User Data Management to the Data Management tab.
3. Optimized Public Data Management.
As system usage time increases, there are loads of datasets in Public Data.
However, many of these data tables have been abandoned or never used, which leads to messy public space and inconvenient management for the admin.
Data Management provided in FineBI allows you and admins to manage the data efficiently.
Public Data Management: You can perform management operations on public data including Unpublish, Stop Update and Delete.
User Data Management: You can perform management operations on the data in My Analysis including Delete.
The super admin can detect, unpublish, stop updating, and delete the tables in the public data.
The subordinate admin can unpublish, stop updating and delete tables in the public data detected and within the administrative rights.
1. Detect the public data.
Only the super admin can perform the operation.
Log in FineBI system as a super admin, and choose System Management > Data Management > Public Data Management to enter the public data management page.
Click Detect Public Data Now to detect all the tables in the public data.
By default, you can check the public data accessed in the past 30 days.
You can modify the setting Detect Access in Last X Day(s) to change dynamic detection range. Setting range: From 1 to 90. Unit: Day.
After you have modified the range, the system will immediately perform a public data detection.
2. Present the detection results.
After the detection is completed, the latest detection results will be automatically displayed on the page. FineBI admins can view a breakdown of public data for which they have management rights.
After the detection is completed, the results will be presented in the form of an itemized table. The detection results include basic information, business using information, system pressure information, and degree of influence.
The detection process is executed in the backend. You can continue the works on other pages.
During the detection process, a detection progress bar is provided for you to know the process.
Last Data Detection Time is displayed, which is helpful for you to plan detection tasks.
3. Re-filter the detection results.
As the amount of public data detected can be very large, you are recommended to re-filter the detection results.
Click Expand Search Panel, select the needed search contents, and click Search to view the corresponding information.
You can click the table field of the tables to sort the detection results.
You can click Export Excel to export the detection results under the current search criteria to an .xlsx format file for business users to confirm.
FineBI admins can select the public data tables displayed in the list to perform the operations.
Operations include Unpublish, Stop Update, and Delete.
The impact and scope of these operations are shown in the following table:
1. It only takes effect on tables whose type is self-service datasets, or tables published from My Analysis to Public Data.
2. Unpublishing on other types of tables do not take effect.
1. It only takes effects on updated tables, not on direct connect tables and the simplest tables.
2. After you set Stop Update for basic tables, the tables here will also stop to update.
Also, the setting of Update Single Table > Update Folder changes to Full first time, no update thereafter, which means that the table will be updated fully when the folder where the table is located is updated, and the table will not be updated thereafter.
3. After you set Stop Update for self-service dataset tables, the table here will also stop to update.
Update Single Table changes to No Update With Parent Table, which means that the table will not update with its parent table.
1. It only takes effect on basic tables, not on self-service dataset tables.
2. After you delete the basic table, the deleted table will be moved to the recycle bin.
3. The influence of deleting a table here is the same as deleting a table in other options.
The detection results and management suggestions are shown in the following table:
Table type
1. It only exists in the table name field as an identifier, not as an independent field.
2. It does not exist in the exported detection results.
Data table includes:
DB table
SQL table
EXCEL table
Self-service dataset: The table published in public data by a user after analysis.
Other tables: Data tables other than the above four types, such as user access logs embedded in FineBI.
The creator of a data table, including the creator's username and name.
Format: Name (Username)
The location of a data table in Public Data.
Format: Public Data/Folder/Folder/Folder
The creation time of a data table shown in the basic table.
A table of the self-service dataset type shows the publishing time when the data table was published from My Analysis to Public Data.
Format: yyyy-MM-dd HH:mm:ss
The tables recently created/published may not have been used yet, so it focuses mainly on the historical tables.
The view times the table, table-associated topics, dashboards, components, self-service datasets have been accessed in the last N days.
The data is taken from the table fine_record_execute table in Logdb. The view times for the following type are calculated:
Subject: type = 501 and 502
Dashboard: type = 101, 102, 105, 106, 107, and 108
Component: type = 301 and 302
Dataset: type = 202
The latest view time that other users (not the creator) visit a table, its associated subjects, dashboards, components, and self-service datasets in the past N days.
If no other users have accessed the data table, the field value is displayed as --.
The update modes for self-service dataset settings include:
Update with a parent table.
Not update with a parent table.
The field value in a direct table, the simplest table, and a basic table is displayed as --.
The latest time that a table is updated successfully.
Format: YYYY-MM-DD HH:MM:SS
The field value of direct connect tables, tables that have not been updated, tables that have failed to update for a long time, and the simplest tables are displayed as empty by default.
The number of creators of all direct or indirect sub-tables/components/dashboards of the table, including the creators themselves.
Whether to enable permission inheritance :
Yes or No
User Data Management is only available for FineBI super admins and not available for subordinate admins.
1. Detect the user data.
Log in FineBI system as a super admin, and choose System Management > Data Management > User Data Management to enter the user data management page.
Click Detect User Data Now to detect all tables under My Analysis.
By default, you can check the user data accessed in the past 30 days.
You can modify the setting Detect Access in Last X Day(s) to change dynamic detection range. Setting range: from 1 to 90. Unit: Day.
After you have modified the range, the system will immediately perform a user data detection.
After the detection is completed, the latest detection results will be automatically displayed on the page. The super admin can view all tables in the user data.
The detection process is executed in the backend. The super admin can continue the work in other pages.
Last Data Detection Time is displayed, which is helpful for the super admin to plan detection tasks.
As the amount of table detected under My Analysis can be very large, you are recommended to re-filter the detection results.
The super admin can select the table under My Analysis displayed in the list to perform the operation Delete.
After you delete the table, the deleted table will be moved to the recycle bin. The influence of deleting a table here is the same as deleting a table in other options.
The detection results and management suggestions are shown in the following table.
Source Table Type
1. It only exists in the Table Name field as an identifier, not as an independent field.
Local Excel files in My Analysis
and Others
The location of a data table in My Analysis.
Format: xx's Analysis/Folder/Folder/Topic
The creation time of the data table
The number of accesses to the table and its sub-resources on the lineage in the last N days, including:
Dataset Edit/Preview
Editing/previewing of all sub-datasets
Editing/previewing of all subcomponents/dashboards/analysis documents of the dataset
Editing/previewing of subcomponents, dashboards, analysis documents of all sub-datasets
Update With Parent Table
Not Update With Parent Table
Format: YYYY-MM-dd HH:mm:ss
The field value of direct connect tables, tables that have not been updated, and tables that have failed to update for a long time are displayed as empty by default.
Extraction table: Yes/No
Direct tables: field values are --
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy