LEARN. PRACTICE. GROW.Concept and mechanism
The dictionary describes tables and columns. Changing an inherited field can affect several descendant tables; a dictionary override permits supported differences on a child table without changing every other descendant. If only incidents need a different default, inspect inheritance before changing Task. Reference fields normally store the related record’s sys_id, although an alternative reference key can be configured. The displayed name does not guarantee unique identity. Two teams can have similar names and different identifiers. Define a stable key and document the distinction between stored value, presentation, and the rule used to find matches.
Guided application
When importing an owner list, first validate input data and transformation rules. Coalesce finds matches to update existing records; without a match, normal configuration allows insertion. With several coalesce fields, all must match. A mutable field such as a description can prevent a match and create duplicates. A nonunique key may update only the first matching record, hiding a quality problem. Review empty values, case handling, and references before transformation. Compare inserts, updates, and rejections against expectations and an identified sample. Coalesce does not automatically clean up old duplicates or replace an identity policy. Repeating the same file without understanding its result can make the problem worse.
Same stable key and different description: coalescing on both can insert.
Common pitfalls
Name as universal key; coalesce treated as deduplication; parent change without impact.
Related topics: Instance, navigation, and context · Configuration, access, and interfaces · Records, collaboration, and analytics
Define identity and expected outcome before transforming.
Reference: Updating records using coalesce · CSA blueprint January 2026