Resource Handover FAQ

Version

Application Scenarios

This document introduces the possible problems that may occur during resource handover and provides corresponding solutions.

During resource handover, a prompt box pops up saying "The department roles of the sender and recipient do not match each other, which may require reconfiguration in the future. Sure to perform handover?".

The department roles of sender A and recipient B are not entirely identical, so the permissions of data for user A and user B may not be entirely identical. In this case, the system would pop up a warning box.

Click OK directly, which would not affect the handed-over resources.

However, users may not have permission to edit or view the corresponding tables after the handover. It is advised to assign the corresponding data permissions to the users. For details, see Overview of Data Permission.

User A has a data table in the business package C. After the table is handed over to user B, user B cannot see it.

User B may not have the viewing permission of the business package C.

Assign the corresponding data permissions to user B. For details, see Overview of Data Permission.

During resource handover, a prompt box pops up with the error message displayed: Handover failed due to system exceptions. Detailed exception information has been recorded in the system log.

View the log, and an error occurs: handover report has lock.

Dashboards being edited cannot be handed over.

After confirming that the sender has exited the dashboard editing page, perform the resource handover operation.

After the self-service dataset created by user A is handed over to user B, user B edits the self-service dataset and a prompt box pops up saying "The permissions for field {Field name} are missing and only null data can be displayed".

The handed-over self-service dataset relies on an original table, and user B does not have the data permissions of that original table.

Assign the corresponding data permissions to user B. For details, see Overview of Data Permission.

After the self-service dataset created by user A is handed over to user B, user B updates the self-service dataset and it prompts that the data limit is exceeded.

The admin has assigned row-level permissions of the self-service dataset to user A and full viewing permissions to user B, resulting in exceeding the data limit during the update.

Assign the corresponding data permissions to user B. For details, see Overview of Data Permission.