Checklist progress
0/316Learned
Platform App Builder
Study Checklist
Checklist progress
0/316Learned
Given a scenario, determine the appropriate data model.
0/14
Given a scenario, explain the capabilities of the various relationship types and the implications of each on record access, user interface, and reporting.
0/14
Given a scenario, determine the considerations when selecting or changing a field data type.
0/19
Text and long-text field types
Learn this conceptNumber, currency, and percent fields
Learn this conceptDate, Date/Time, and Time fields
Learn this conceptCheckbox versus Yes/No picklist
Learn this conceptEmail, Phone, and URL field types
Learn this conceptPicklist versus multi-select picklist
Learn this conceptRestricted versus unrestricted picklists
Learn this conceptDependent picklists and controlling fields
Learn this conceptRecord types and picklist values
Learn this conceptAuto-Number field configuration
Learn this conceptExternal ID and unique field types
Learn this conceptFormula versus stored field types
Learn this conceptUniversally required versus page-layout required fields
Learn this conceptCustom field type conversion data loss
Learn this conceptBlocked custom field type changes
Learn this conceptGiven a scenario, determine the options and considerations when importing and exporting data, including the capabilities of external data sources.
0/9
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.
Changing a custom field's data type can erase or shorten the values already stored in that field, because the new type cannot always hold what the old type stored. Salesforce recommends converting only empty custom fields for that reason. Loss is not automatic for every type pair: some conversions keep the stored value, some keep only a truncated prefix, and some wipe the field to null.