Section 3 · Data Modeling and Management · 20% of exam
3.2 Choose Field Types and Manage Schema Changes
Exam objective
Given a scenario, determine considerations when selecting or changing Salesforce field data types. Field types shape data validation, storage, user entry, formulas, filters, integrations, and reports. Use a type that reflects the meaning of the value rather than its current display. Currency should represent amounts; date and date-time distinguish calendar dates from moments; percent expresses a ratio; checkbox captures a true/false state; email, phone, URL, and address components provide purpose-specific behavior. Text is flexible but sacrifices type-aware validation and calculations. Picklists constrain choices and can improve consistency, but require governance as values evolve. Before adding a field, confirm whether an existing standard field can serve the use case. Decide whether the field should be required, unique, external ID, encrypted, indexed through supported features, or available in reports. Consider whether the value is entered directly, derived in a formula, synchronized from another system, or managed by automation. Formula fields are calculated and read-only to users; they are not a place to store a historical snapshot. A stored value may be needed when the business must preserve what was true at a specific point in time. Changing field types can alter data interpretation or fail because existing values cannot convert. Salesforce restricts some conversions, especially where relationships, formulas, integrations, or automation depend on the field. Picklist changes can affect existing values, dependencies, record types, imports, and reports. Converting text to a number, date, or picklist requires data cleanup and a mapping plan. Review dependencies before making a schema change; the field may appear in flows, formulas, validation rules, page layouts, reports, and external integrations. Salesforce Certified Platform App Builder | SU ·26 guide alignment 9 Use field labels and descriptions that match the business vocabulary. API names become part of integrations and metadata, so choose stable, clear names. Provide help text for non-obvious entry rules. Protect sensitive data with field-level security and apply retention or encryption requirements where appropriate. Test with sample values, imports, locale-specific date and number formats, and users with different permissions.
Applied scenario: A company stores an annual renewal percentage and wants to calculate projected revenue. Represent the rate as a percent and the money as currency, then create a formula only if the projection should always reflect current source values. If finance needs a frozen value at the time a contract is approved, capture a snapshot through controlled automation instead of relying only on a formula. Before release, test decimal precision, blank rates, currency behavior, imports, downstream reports, and field visibility for users who should not see financial data. Design and risk review: Do not change a field type in production before checking dependencies and conversion behavior. Data that looks numeric may contain punctuation or nonnumeric characters. Date-times can shift when displayed in different time zones. Picklist values can be retired while historical records still contain them. A field marked required at the database level can affect integrations and legacy records differently from a field merely made required on a page layout. Keep the desired data quality rule explicit and test all entry paths.
Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.
Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.
Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.
Key takeaways
- Given a scenario, determine considerations when selecting or changing Salesforce field data types
- Choose the platform feature that fits the requirement, data, access, and operating context.
- Test realistic users, exceptions, dependencies, and lifecycle effects before release.
- Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/data_modeling
