This article will introduce some notes and error messages when you synchronize users.
Sub-admins are unable to add users in certain situations.
User Source
Problem
Synchronize Users is not enabled.
Sub-admins only have access to Add User and Import User, but have no access to Synchronize Users.
Synchronize Users is enabled.
Sub-admins only have access to Add User and Import User, but have no access to Synchronize Users Management.
Problem:
The created server dataset can be previewed, but when you use this dataset to synchronize/import users, there are no selectable fields.
Cause:
Check the log and find the error message: SQLServerException: Invaild object name 'datal'.
Check the method of creating the dataset. In a server dataset using a stored procedure, SQL execution will fail after nesting.
After you configure the ID column, ID verification will be operated to prevent conflicts during data insertion. Any data that fails this verification will also be listed in the result panel. Below are some of the error messages that may appear in the panel.
Error message:
Cause: As long as you fill in the name, the corresponding ID should be filled in as well.
Cause: After selecting an ID, you can change the username but cannot change the ID, otherwise an error message of ID conflict will occur. For example, due to the ID conflict, Alice's ID used to be 3 and now it is changed to 2.
Cause: When multiple usernames use the same ID, an error message will occur.
Cause: When a username corresponds to multiple IDs, an error message will occur.
When you synchronize a tree dataset, the synchronization often fails due to issues related to the tree dataset construction.
Note:
1. Department identity: the original identity field selected when you construct the tree dataset.
2. Parent department identity: the parent identity field selected when you construct the tree dataset.
Error message: report, decision-making platform original identities are the same.
Cause: In a tree dataset, multiple departments use the same identity. For example, the did field value of both report and decision-making platform is a12.
Error message: report has multiple direct parent departments.
Cause: A department has multiple parent department identities. For example, the pid field in the following report has a1 and a2.
Error message: decision-making platform could not find the corresponding parent department.
Cause: If the parent department identity is empty, this department is the root department. If it is not empty and the corresponding department cannot be found based on the parent department identity, an error message will occur.
For example, the pid field value of decision-making platform is a3, but no department's did field value is a3. This means that there is no such parent department.
Note: When you synchronize user datasets, if the server dataset is a tree dataset, the parent organization value of the top-level organization should be empty.
Error message: report has multiple original identities.
Cause: If the department names are the same and the parent department identities are the same, it means that they are the same department. If their department identities are different, an error message will occur. For example, the report has two did field values, a13 and a12.
Error message: decision-making platform, FanRuan Software, DEC R&D constitutes a parent-child structure infinite loop.
Cause: If the parent identity of department 111 points to department 11, the parent identity of department 11 points to department 1, and the parent identity of department 1 points to department 111, a loop is formed, which will result in an error.
For example, the parent identity for FineReport Software is a111, which points to DEC R&D. The pid for decision-making platform is a1, which points to FineReport Software, and the pid for DEC R&D is a11, which points to decision-making platform.
Error message: Duplicate name with other source object.
Cause: The imported dataset contains duplicate data, which will result in an error. For example, if tree dataset A is synchronized first, importing tree dataset A again will result in this error.
Error message: ID duplicates with other source objects.
Cause: The platform has a built-in department 2. When you synchronize a tree dataset for the first time and choose to preserve update permissions, an error will occur after synchronization if a synchronized department 1 and the built-in department 2 in the data source have the same ID but different names.
In a tree data set, if you select the department ID which is not the department tag column, ID verification will be operated, which will result in a global failure. In all the following examples, the department tag column is referred to as did, the parent department tag column as pid, and the department ID column as depId.
Error message: the department tag value of FanRuan software is inconsistent with the department ID.
Note: This error message will not occur in FineBI version of August 3rd, 2020 or later.
Cause: If the department tag only consists of numbers, such as 11 or 111, it will be directly inserted into the department table in finedb as an ID item. In this case, if the platform also selects another column as the department ID, and the department tag value is not the same as the selected department ID, an error will occur. It is recommended to use SQL statement string concatenation with an English letter when the data source's department tag only consists of numbers.
Error message: FanRuan Software ID is empty.
Cause: In a tree dataset, if you select the department ID which is empty, a global error will be reported directly.
Error message: FanRuan Software-report ID is duplicated. Duplicated object: FanRuan Software-decision-making platform.
Cause: FanRuan Software-report and FanRuan Software-decision-making platform use the same department ID.
Error message: FanRuan Software-report corresponds to multiple IDs: 15/12.
Cause: This error occurs when a department has multiple IDs. For example, the FineRuan Software-report department corresponds to two department IDs, a12 and a15.
Error message: decision platform and original ID conflict.
Note: This error message will not occur in FineBI version released after June 8th, 2020 or later.
Cause: The error occurs when the department ID is changed and conflicts with the original department ID.
Error message: This time, the number of synchronization users will be reduced by 56%(5), reaching the set interruption value of 30%. Please check whether the data source is normal, or temporarily disable the "abnormal data interruption".
User synchronization is highly dependent on the data source. If there is something wrong with data source, such as being maliciously cleared of database tables, the users synchronized to the system will be cleared, and the operation cannot be reversed. Therefore, FineReport provides a synchronous circuit breaker strategy. In FineBI of version 5.1.15 and later, a Synchronize Abnormal Data Interruption button is added. After the admin enables it, you can set the synchronization to stop when the number of users decreases by X%, and X is a positive integer from 1 to 100. For example, if there were originally 100 synchronized users (excluding manually added/imported users) in the system and the decrease rate is set to 30%, then synchronization will be stopped when at least 30 (100*30%) users are cleared out.
After you install and use the plugin Sync LDAP Domain Users, the user synchronization fails, and an error message will occur:
Failure reason: 21307213 - illegal node
User is under User:
User 1 --> User under user
Department is under User:
User 2 --> eng = user under department, eng = xxx, eng = xxx, eng = roles, o = fanruan, dc = fr, dc = com
Role is under User:
User 3 --> Role under user
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy