Now that we have a good understanding of the various field types that are available and sales force
let's take a quick look at some of the considerations that we need to have in mind.
While conducting field types so in sales force we have the option of converting field type changing
from one field type to another.
So why do we do so.
What are all the things that we need to have in mind.
First comes the auto number.
So it says auto number can be converted to other data types but will encounter data loss in samples.
We have a different date field types from auto number formulas all up summary.
These are the relationship field types.
So basically these auto number form level up somebody they are system generated fields.
We do not provide any input to these field types.
They look up the relationship master detail external look up all the other relationship types they are
the relationship fields and the others they are then generally field types.
So then that is a field which is of type auto number.
Salesforce gives you an option to convert to other field types however you'll encounter complete data
loss.
You have to upload data for the new field
roll up summary cannot be converted to any meaning.
If that is a roll up summary field and if we tried to convert it to other field types we can't basically
do that.
We can't convert that all up somebody's feed to other data types say for example this is the department
object and we have it all up somebody field here and that field is a comp of the instructors number
of instructors map to that particular department.
So this is all up somebody field.
When I hit the edit button I do not see that option off change field type.
We do not have that button at all meaning roll up somebody fields can be converted to other field types
perfect moving on similar behavior with the formula fields aspect formula fields can't be converted
to other data types look up in master detail can be converted to each other.
Yes lookup can be converted to master detailed master data can be converted to look up there are some
considerations while doing that which we'll discuss in detail in the forthcoming sessions.
However there is a possibility checkboxes can be converted to other data right but will encounter data
loss meaning Salesforce gives you an option to convert checkbox field type to other field types but
then they'll encounter complete data loss.
This is similar to auto number and currency is a little different.
It comes with certain criteria meaning currency can be converted to other data types.
However the data loss depends on the field that we are converting to.
If we convert currency fields to email no percent form text text area or text area along on your model
then we will not encounter any data loss.
But if we convert currency field to other fields then we would encounter data loss
data can be converted to other data but with complete data loss.
Yes same behavior with the daytime same behavior with time you can convert it but that would be 100
percent data loss email also comes with a certain restriction though we can convert it.
There are a certain field types to which there would be no data loss and text text area text data along
a new water.
However for other fields that would be complete data loss geo location feels we can't convert to any
other data types that option in itself will not be available.
No can be converted.
And for some of the field types we'll have the data present.
But for the other field types it will be complete data loss
similarly 4 percent field types as well.
If we convert to currency e-mail no phone text text area text area along a new water.
That would be no data loss but if for other field types that would be data loss similar behavior for
phone for email text text daily attacks data along and you worry that if we know data loss but for the
other field types there will be data loss
backlist that is an option to convert to other data types.
But if backlist is converted to my pick list the inactive list values will be lost.
Only the active pick list of values will be present.
But if we choose other data types then all the data will be lost.
The MSP we can convert but complete data loss will be there and for text it comes with the restriction.
If we change to order no email pick list text exterior text data along on you.
Then there will be no data loss.
But for others it will be a data loss for next area.
Also for phone email text X data along on you all that will not be any data loss but for other field
types that will be data loss for text data along.
We have a partial data loss actually that does appear to have different characters to email phone text
X data you water.
But for others it could be complete data loss and text data adage we can convert only to text data along
say for example in our data model in the extracurriculars object details field that is that exterior
Ridge field so if we tried to convert that field we are in the extracurriculars object this object definition
page and this is that next data outage field so let me now try to change the field type only text area
along is available.
Meaning we can convert the text area rich fields to only text area long fields but the hedge GMO content
will be lost because it attacks Syria along.
It does not support any to a malcontent and a text encrypted field.
It can be converted to any other data types you want and can be converted.
But if you convert the email form text exterior text data along that will not be any data loss but for
other field types.
That will be data loss.
So these are some of the conservations that we need to note while converting field types.
In fact many of these I learned by trial and error by experimenting more of the different field types
so you can also try creating different field types.
Try converting them to other field types and see their behavior.