An app builder at Northern Trail Outfitters needs to change the data type of some custom fields. The org has already met the field limit on the object and would like to limit recreating fields.
What data type change limitations should the app builder consider?
When considering data type change limitations, one important restriction is that Salesforce does not provide an option to change a field type directly from text to an encrypted field. This process requires deleting the existing field and creating a new one to accommodate the encrypted data type. Consequently, this would necessitate recreating fields, which the app builder at Northern Trail Outfitters aims to avoid. Therefore, it is crucial to recognize this limitation to avoid complications.
ASNWER: ABC This question is similar to Question #99, except the scenario isn't asking about what answer would require an extra step. It's written more like a "Choose three" question, because it asks "What data type change limitations should the app builder consider?". Since there are three answers that contain limitations to consider and only one answer that contains a data type conversion that wouldn't have any problems (D), the other three answers must be what the question must be about. A. Changing the data type of a field used in a report from text to an encrypted field "...an existing custom field can’t be converted into an encrypted field nor can an encrypted field be converted into another data type." i.e. it can't be done without deleting and recreating the field which the app builder will NOT be doing in order to limit recreating fields as it states in the scenario. So, a problem to consider.
B. Changing the data type of a field used in an Apex class from number to text "You can’t change the data type of a custom field referenced by other items in Setup such as Visualforce pages, Apex code, processes, or flows." This would require the extra step of removing all apex references, etc. and would therefore also be a problem to consider. C. Changing the data type of a field used in lead conversion from number to text "You can’t change the data type of any custom field that is mapped for lead conversion." A custom field mapped in lead conversion would need to be unmapped, converted, then mapped again. Again, a problem to consider. NOT: D. Changing the data type of a field used as an External ID from number to text "If you change the data type of a custom field that‘s set as an external ID, choosing a data type other than text, number, or email causes the field to no longer act as an external ID." This conversion causes no issue with the external id field acting as an external id field, so there is no problem to consider here.
https://help.salesforce.com/s/articleView?id=sf.notes_on_changing_custom_field_types.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.notes_on_changing_custom_field_types.htm&type=5
The important factor in the question is the limitation of field creation and there is only one answer that forces a new field to be created. A A) Requires a new field to be created. ---------------------------------------------------------- B) Requires rewriting APEX code but no new field needs to be created. C) Requires un-mapping, converting and remapping but NOT creating a new field. D) Is not a problem so no new fields need to be created. See Jason_R's explanation for each below.
A. Changing the data type of a field used in a report from text to an encrypted field B. Changing the data type of a field used in an Apex class from number to text The app builder should consider the following data type change limitations when changing the data type of a custom field: Changing the data type of a field used in a report from text to an encrypted field: This is not allowed as encrypted fields cannot be used in reports. If a field used in a report is changed to an encrypted field, the report will break and will need to be recreated. Changing the data type of a field used in an Apex class from number to text: This is not allowed as Apex code written to access the field data will break if the field data type is changed from a number to text. The Apex code will need to be modified to correctly handle the new text data type.
Answer is A, Salesforce doesnt provide option to change field type from text to encrypted, and forces us to create a new field. I have tried this.