Sync/Import User FAQ

This article introduces some precautions and errors when synchronizing users .

In some cases, sub-admins cannot add users, as shown in the following table:

Problem Description:

The created server dataset can be previewed, but when synchronizing /importing users with this dataset, there are no fields to choose from, as shown in the following image:

Cause Analysis & Solutions:

Check the log and find an error: SQL ServerException : Invalid object name 'data1'.

Check how the data set is created, such as the server data set of the stored procedure class, the SQL execution fails after nesting.

the ID column is configured , some ID checks will be performed to prevent conflicts during storage. The data in error at this point is also listed in the results panel. Below is a list of errors reported.

1. ID is empty

error message is shown in the following figure:

Reason: After id is checked , the situation where name is not empty but id is empty is not allowed. As shown below:

2. Conflict with original ID

error message is shown in the following figure:

Reason: Change the username after checking ID, but it is not allowed to change the ID, otherwise an ID conflict error will be reported. For example, Alice's id is 3, but now it is changed to 2.

3. ID duplicates with other objects

error message is shown in the following figure:

Reason: As shown in the figure below, an error occurs when multiple usernames use one id.

4. Corresponding to multiple IDs

error message is shown in the following figure:

Reason: As shown in the figure below, this error is reported when a user name has multiple ids.

When the synchronization data set is a tree data set, the synchronization often fails due to the construction of the tree data set. Various situations are listed below:

Note: noun explanation

• Department Tag: The original tag field chosen when building the tree dataset.

• Parent Department Tag: The parent tag field selected when building the tree dataset.

1. 21300055-Report, DEC interaction original tag is the same

The error message "report and DEC interaction original tags are the same", as shown in the following figure:

Reason: In the tree dataset, multiple departments are marked with a department, such as the DEC interaction in the figure below, and the did of the report is a12. As shown below:

2. 21300056-Report has multiple immediate parent departments

The error message "The report has multiple direct parent departments", as shown in the following figure:

Reason: A department has multiple parent department tags. For example, the pid of the report in the following figure has a1 and a2.

3. 21300057-The decision platform cannot find the corresponding parent department

The error message "The tree construction failed, the decision-making platform cannot find the corresponding parent department", as shown in the following figure:

Reason: If the parent department mark is empty, then this department is the root department. If it is not empty and the parent department mark cannot find the corresponding department, an error will be reported.

As shown in the figure below, the pid of the decision-making platform is a3, but no department has a did of a3, that is, there is no parent department :

Note: When synchronizing user data sets, if the server data set is a tree data set , the parent organization of the top-level organization should be null.

4. 21300058 - Report has multiple raw tags

The error message "The report has more than one original tag", as shown in the following figure:

Reason: If the department names are the same and the parent department tags are the same, it means that this is the same department. If their department tags are different, an error will be reported. There are two didids in the report in the following figure: a13, a12.

5. 21300059 - Parent-child structure infinite loop

The error message "Decision report, FanRuan software , DEC research and development constitute an infinite loop of parent-child structure", as shown in the following figure:

Reason: If the parent tag of department 111 points to department 11, the parent tag of department 11 points to department 1, and the parent tag of department 1 points to department 111, forming a ring, an error will be reported.

As shown in the figure below, the parent tag of FanRuan software is a111, which points to DEC research and development, the pid of the decision-making platform is a1, which points to Fanruan software , and the pid of DEC research and development is a11, which points to the decision-making platform.

6. 21300063 - Duplicate name with other source object

The error message "Duplicate name with other source objects" is reported, as shown in the following figure:

Reason: The department that imported the tree dataset has data that is duplicated with that of the synchronization department. If the tree dataset A is synchronized first, and then the tree dataset A is imported, this error will occur.

7. 21300064-ID duplicates with other source objects

The error message "ID is duplicated with other source objects" is reported, as shown in the following figure:

Reason: The platform has built-in department 2. When synchronizing a tree data set for the first time, choose to keep the permission to update. The ID of a synchronization department 1 and built-in department 2 in the data source are the same, but the names are different, and an error will be reported after synchronization.

case of tree datasets , if the department id is also checked , and the department id column is not the department mark column, id verification will be performed, which will cause a global failure. In all of the following examples, the department tag is listed as did, the parent department tag is listed as pid , and the department id is listed as depId .

1. 21300054-Department tag value is inconsistent with department ID

The error message "Department tag value is inconsistent with department ID" is reported, as shown in the following figure:

Note: For JARs of 2020-08-03 and later, this error code will not appear.

Reason: If the department is marked as a pure number, such as 11, 111, it will be directly inserted into the department table of finedb as an id item. At this time, if the platform has checked other columns as the department id, and the department marked value and the checked department If the id is different, an error will be reported. It is recommended that when the data source is marked as a pure number, use the string of the sql statement to concatenate an English letter.

2. 21300053-ID is empty

The error message "ID is empty" is reported, as shown in the following figure:

Reason: In the case of tree data set , if the department id is empty after checking the department id, a global error will be reported directly. As shown below:

3. 21300051 - Report ID duplicated with other objects

The error message "Report ID is duplicated with other objects" is reported, as shown in the following figure:

Reason: FanRuan Software -Report and FanRuan Software -Decision Platform use the same department id. As shown below:

4. 21300050-Report corresponds to multiple IDs

The error message "The report corresponds to multiple IDs" is shown in the following figure:

Reason: This error will be reported when there are multiple department IDs in the department. As shown in the above figure , the FanRuan software -report has two department IDs, a12 and a15. As shown below:

5. 21300052 - Decision-making platform and original ID conflict

The error message "decision platform and original ID conflict" is reported

Note: For JARs of 2020-06-08 and later, this error code will not appear.

Reason: The department id has changed, and an error will be reported that conflicts with the original department id

The error message " 21300031 - The number of synchronization users will be reduced by XX% (XX ) this time , reaching the set interruption value of XX%. Please check whether the data source data is normal, or temporarily disable the "abnormal data interruption synchronization" function."

As shown below:

reason:

The synchronization user is highly dependent on the data source. If there is a problem with the data source, for example, the database table is maliciously emptied, the user synchronized to the system will be emptied, and the operation cannot be reversed.

Therefore FineReport provides a synchronous fusing strategy. For BI projects of version 5.1.15 and later, the button "Synchronize Abnormal Data Interruption" has been added.

After the administrator enables "Abnormal Data Interruption Synchronization", the number of users can be reduced to X% and the synchronization can be stopped. X is a positive integer from 1-100.

For example, if the original 100 synchronization users in the system (excluding the number of manually added/imported users) are set to 30%, that is, if the synchronization decreases by 30 (100*30%) users or more, the synchronization will be stopped.

Ⅷ. 21307213-Illegal node

After installing and using the plugin "Sync LDAP Domain Users", the synchronization of users fails, and the error message is reported:

Failure reason: 21307213 - illegal node

Users under Users:

user1-->Users under the user

Departments are under Users:

user2--> cn =user under department, cn = xxx,cn = xx,cn = roles,o = fanruan,dc = fr,dc =com

The roles are under the user:

user3-->User role"

As shown below: