Skip to main content
  • Only English table names are supported.

​
Q: When Creating a Data Source, the Error “Connection Test Timed Out. Check the Connection Information and Firewall, Then Try Again” Appears

  • When integrating a Data Source with your own system, ensure your database or system is accessible over the public network. Otherwise, this error occurs.

​
Q: When Using SQL Server (Versions Earlier Than 2012), the Error “Xxx Field Is Not a Recognized Built-In Function Name” Appears

  • YiDA is not currently compatible with SQL Server versions earlier than 2012. Data may occasionally display correctly, but these versions are not recommended.

​
Q: Trigger Rules Between Form Submission, Bulk Import (Trigger on Selection), OPEN API / Page Data Source, and Business Association Rules or Integration & Automation

  • Not supported.
Use the following allowlist configuration for the network of YiDA external Data Sources and business services.
Yes. A subform can serve as an independent dataset and be selected for cross-app data retrieval.
Cross-app data is currently supported only in report scenarios. Form data linkage, multi-table association, and other scenarios will be supported gradually in the future.

​
Q: When Will the Attendance Dataset Be Available?

A: It is on the roadmap and will be considered for delivery in future iterations.

​
Q: Why Can’t I Preview the Latest Data in the Official Dataset I Connected To?

A: You currently need to manually click the test button to refresh the data. A refresh button for preview data will be added later.

​
Q: Is the Data Real-Time or Updated the Next Day?

A: Currently, only [OA Approval] data is real-time. General metrics, employee roster, Smart HR (onboarding, transfer, promotion, resignation), and similar datasets are updated by default at 00:00 the next day.

​
Q: After an Admin with Data Permissions for a First-Party App Creates a Dataset via Data Factory, How Can Data Permissions Be Further Configured?

A: Data processed through Data Preparation generates a new independent dataset based on the data permissions of the most recent publisher. The default row and column permissions of this dataset depend on the last publisher’s permissions. On this basis, you can configure independent dataset permissions.
A: Only OA Approval data generated within the past year is currently available.
Floating-point conversion is currently required. A floating-point formula function will be provided in the future.
After adding new components, click test again or drag the dataset in again to update it.
The number of data rows shown in the data preview within Data Preparation is for reference only. It cannot be used to judge the final output dataset row count, because intermediate acceleration caching may exist.
For example, if the nodes are structured as A - B - C, modifying the field type of node A affects only nodes B and C. Modifying the field type of node B affects only node C.
In daily use, avoid irreversible delete or reset actions on data operation nodes.
  • If the content of a preceding processing node changes (for example, it contains a field A with field ID = xxx001), including deleting and re-adding the node, a completely new field ID is dynamically generated for subsequent fields (the ID of field A may be randomly regenerated as yyy789, for illustration). This causes existing node ID configurations in downstream business consumption scenarios such as reports and dashboards to fail.
In YiDA, the exposed field “first check-in time” uses the format: yyyy-MM-dd HH:mm:ss.Display rules:
  • If the user has a shift schedule and clocks in for the first work shift, the time is recorded as the first check-in time of the day.
  • For Approval forms, out-of-office, leave, supplementary check-in, and field work records are not counted.
  • For check-in records, field work and admin-modified records are not counted.