Why Doesn’t My Destination Reflect an Updated Salesforce Data Type?

You may notice that after updating an object's data type in Salesforce, the corresponding destination column reflects the original data type. This may also result in formula field translations errors.

Why the data type isn't updated

This issue occurs when you update an object's data type to a smaller type that occupies less memory space, such as from STRING to DOUBLE. When this happens, the destination reflects the original, larger data type.

In addition, we produce formula field translations based on the Salesforce object's current data type, not the data type of the column in the destination, which may result in a conflict. When this happens, you may encounter errors.

How to fix data type mismatches in your destination

To resolve this issue, do the following:

1. Create a new column in your destination with the updated data type.
2. Copy the data from the old column to the new column with a CAST function that converts the data to the new type.
3. Rename the old column to reflect its deprecation.
4. Rename the new column to match the original column name.
5. Drop the old column.