Use the checkling to help you resolve dependencies before you delete records.
When you delete records, you must remove any associated references to the record in related records. Before you delete a record, review the information that is provided here.
Object | Delete implications and precautions |
Assets |
Deleting also removes references in associated user, stockroom, and software records. |
Audits | If you delete a stockroom, the audit and its related history are also deleted. |
Accessories |
You must deprecate the accessories in the stockroom before you can delete the accessories. |
Contracts |
When you delete a contract, it is automatically removed from the software record. |
Custom objects |
If you use a custom object to populate a dropdown list, and an option in the list is selected in a record, the dependency checker will prompt you to remove the related dependencies before you delete the custom object records. |
Integrations |
|
Locations | You must resolve references in records to the location that you want to delete before you delete a location. For example, the location might be referenced in stockroom, asset, and user records. |
Request offerings |
When you delete a request offering, the request offering is deleted from the portal, so no further requests can be submitted. If you want to delete a request offering category or status, you must resolve the dependencies before you delete them. You must delete the workflow associated with the request offering, as it will still exist in the system. |
Software |
If users were assigned a specific software, you must archive the users before you delete the software. You must remove the association between the software and the contract before you delete the software permanently |
Stockrooms |
Assets and accessories must be removed from the stockroom before you archive a stockroom. |
Comments
0 comments
Please sign in to leave a comment.