海角天涯社区

Avoiding accidental data loss with when deploying custom field type changes

Avoiding accidental data loss with when deploying custom field type changes

Catherine Bacon on

Share with



Deploying changes to the type of a custom field can be problematic, particularly when there鈥檚 data in the target org. 海角天涯社区鈥檚 new problem analyzer can help you out.

Deploying changes to type

Deploying changes to the type of a custom field can be challenging. Different metadata types have outlinging what can be changed and when. If data exists for those fields in the target, things get even more tricky as deploying the change to the type could lead to the loss of data.

If you鈥檙e making changes to an org, Salesforce will warn you if the change you鈥檙e making could cause you to lose data: Changing to the selected datatype will cause you to lose all existing data in this field.

This is really helpful when making manual changes in the Salesforce UI, but what if you鈥檙e using source control? It鈥檚 easy to change the type of a field, and if you deploy a change to the type of a field you didn鈥檛 mean to, you might lose some of your oraganisation鈥檚 data.

Salesforce DevOps in the age of AI: is your custom pipeline ready?

Find out more

The new problem analyzer

海角天涯社区鈥檚 problem analyzer will look for fields which have a different type in the source and target. If we find any, we鈥檒l warn you about them and you can choose how to proceed.

Analysis results page showing a warning when a custom field has a different type in the source and target

With this new analyzer, you can safely push changes to and from source control without risking accidental data loss because of a changed custom field type.

More successful deployments

This is just one example of how 海角天涯社区 makes more of your Salesforce deployments work the first time. Start your of 海角天涯社区鈥檚 Salesforce metadata deployment solution to see for yourself how much easier and faster your releases can be.

Ready to get started with 海角天涯社区?