Which of the following statements are true regarding the deletion of a custom field? (Select 2 options)
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: A and C
To delete custom fields, they shouldn't be referenced elsewhere.
Deleted custom fields and their data are stored until your org permanently deletes them or 15 days has elapsed, whatever happens first.
Until that time, you can restore the field and its data.
There is no option in Salesforce to deactivate a custom field but you can deactivate the value of a picklist field.
Reference:
The correct statements regarding the deletion of a custom field are:
A. You cannot delete a custom field that is referenced elsewhere C. You have up to 15 days to restore the custom field and all the data stored
Explanation:
A. You cannot delete a custom field that is referenced elsewhere: If a custom field is referenced in a workflow rule, validation rule, formula, Apex code, or any other customization, Salesforce will prevent you from deleting the field. You must first remove the references to the custom field in all relevant places before attempting to delete the field.
B. Once you delete a custom field all data will be permanently deleted: This statement is false. When you delete a custom field, the associated data is not immediately deleted. Instead, the data is moved to the Recycle Bin, where it can be restored or permanently deleted. However, if you empty the Recycle Bin or wait more than 15 days, the data will be permanently deleted and cannot be restored.
C. You have up to 15 days to restore the custom field and all the data stored: When you delete a custom field, Salesforce moves the associated data to the Recycle Bin, where it can be restored for up to 15 days. During this time, you can restore the custom field and all the data stored with it.
D. You can only deactivate a custom field: This statement is false. You can either delete or deactivate a custom field. Deleting a custom field permanently removes the field and its associated data, while deactivating a custom field removes it from the page layout and API access, but retains the field and its data in the database.