Independently Deployed FineDataLink Reading Data from FineBI Public Data

Version

FineDataLink Version	FineBI 6.1 Version	Functional Change
4.0.27	Minimum supported JAR package version: 6.0.12 (2023-08-03)	/
4.0.29	Minimum supported JAR package version: 6.0.13	Allowed using BI SQL dataset parameters in scheduled tasks. Note: Date-type parameters were not yet supported.
4.1.3	Minimum supported JAR package version: 6.0.16	Required no file configuration. Allowed reading data from multiple FineBI projects through data connections. Meanwhile, restricted permission by specifying user accounts and passwords to enhance security.
4.1.14.1	Minimum supported JAR package version: 6.1.4	1. Allowed searching for the directory and table when public data was read. Allowed keeping and displaying the path after selecting a data table. 2. Allowed selecting fields and filtering data rows when public data was read.

Application Scenario

You may want to read public data from FineBI to:

• Use it in business systems such as CRM.

• Display it in FineReport reports.

• Push it to the specified software for notification

Function Description

You can further process data from FineBI in independently deployed FineDataLink projects using Remote Public Data of the Data Synchronization node, the Dataset Input operator of the Data Transformation node, and the Parameter Assignment node, and write the data into a specified database.

You can output data processed in FineBI to designated systems via APIs.

You can write processed data in FineBI into business systems.

FineDataLink V4.1.3 and Later Versions

• Currently, the minimum versions of FineDataLink and FineBI that support this function are 4.1.3 and 6.0.16 respectively. Ensure the project versions are correct. For details, see Version Compatibility Description.

• Create a data connection to connect FineDataLink to FineBI first. For details, see Connection to Remote Public Data.

Note:

If you have read data from FineBI in FineDataLink of versions before 4.1.3, after the project is upgraded to V4.1.3 and later versions, a data connection named Public Data 01 with an empty username and password will be automatically created under Data Connection > Data Connection Management. You need to fill in the username and password, test the connection, and save the data connection.

You need to manually enter the username and password in the Public Data 01 data connection, and test and save the connection.

You want to write the Recruitment Data data table that has been processed and published to Public Data of FineBI into the specified database MySQL for subsequent use by other systems.

Creating a Task

Log in to the independently deployed FineDataLink project, click Data Development, and click New to create a scheduled task, as shown in the following figure.

Configuring a Scheduled Task

Drag a Data Transformation node to the editing page, click the node, and add a Dataset Input operator, as shown in the following figure.

Note:

The Data Synchronization node also allows using public data as the data source, as shown in the following figure.

Select Remote Public Data and select the TRIPS data table that needs to be processed from the public data tables on which you have permissions, as shown in the following figure. In V4.1.13.4 and later versions, searching for the directory and tables is supported.

Click Partial Table Selection to select the specified fields from the FineBI data table.

Filter the specified data.

Note:

The table and field selection function of the Dataset Input operator is the same as that of the Data Synchronization node.

The filtering function of the Dataset Input operator is the same as that of FineBI. For details, see Filter.

Click Data Preview to view the content of the TRIPS table in Public Data, as shown in the following figure.

Output the data with the DB Table Output operator, as shown in the following figure.

Effect Display

After running the scheduled task, you can see that the data in public data is written into the specified database.

If you select a SQL dataset with parameters in FineBI, as shown in the following figure.

Set the same custom parameter area after setting the SQL dataset as the data source in FineDataLink. The default value is East China. You can then click Data Preview to view the data of East China in public data, namely, the parameters in public data are effective, as shown in the following figure.

Note:

For extracted SQL tables in FineBI 6.1, the parameters in FineBI are used for previewing and running in FineDataLink since the parameters with the same name in FineDataLink are not effective. For directly connected SQL tables, the parameters in FineBI are used for previewing in FineDataLink, and the parameters with the same name in FineDataLink are used for running.

Then you can process the data in other ways, such as using the Field Setting operator to remove the value field, as shown in the following figure.

Use the DB Table Output operator to store the data in the specified database, as shown in the following figure.