Issue Summary

This is reproducible on Data Center: Yes

Steps to Reproduce

1. Create 2 Object Schemes (Example A and B).
2. Grant a user of your choice Admin privileges on B and User privileges on A.
3. Enable "Allow others to select objects from this schema" option from Schema configuration.
4. Create an attribute for any object type in A, that refers to an object type in B.
5. Create an outbound reference to objects in schema B in schema A using the attribute you configured in step 4.
6. In Schema B Try to delete the object you have referred in step 5 using the user from step 2.

Objects in Schema B have inbound references from the object schema A in this case. When you delete an object from Schema B, it deletes the object as well as the references to it. Specifically, the delete action should erase all outbound references to this object in the schema A. Outbound references cannot be removed if the user does not have access to the Schema A. 

Users should have Admin privileges in both object schemas if there are references between them in order to delete an object. So this behaviour is not a defect and that this error is intended.

But the error message that appears in this case is very unclear. The purpose of this bug is to include a suitable error message that explains why the object deletion is unsuccessful. End users are currently unable to clearly comprehend why the deletion failed simply by viewing the error.

Expected Results

A clear error message that informs the user that proper permission is required to delete the object.

Actual Results

The below error appears while deleting an object.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available