Changing a field type from Text to Number should not clear existing data. It should try to do the conversion and set values to null (or some other error value) if error, or report on error records. It is quite likely that a field being changed from Text to Number will have valid number values.
My situation is:
I created several custom (external ID) fields as Number fields, only to discover that the values were being displayed with the thousand separator.
So I changed the fields to Text fields. This resulted in all my values having an extra '.0' on the end. Which is why my Upserts and Selects didn't work. (I have created a case for this bug).
I didn't want to go through the effort of fixing the values as there is no nice mass update tool.
I want to change the fields back to Number but I get a warning that all my data will be lost.
Now I'm backed into a corner and I am forced to update/reload ALL my 100,000's records.
1 Comment » Posted by dchang11282007
Posted Feb 12
Categories: Customization, Database Services, Force.com Platform, Administration & Sharing
|
dchang11282007 Mar 2 |
Similarly, changing field type from Date to Date/Time and vice versa should not clear data. |