--- schema_version: "1" id: 449cbd48a3460dedf4e50726a111917f3bf28d0703f30af5f2782d9c92220834 title: Cross-Object Field Updates collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/workflow_cross_object_field_updates.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.workflow_cross_object_field_updates.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 921b6fe2106fa79b29973c0c3c8bb5f3599bcb722b8a07f191473bc3633b9504 description: For all custom objects and some standard objects, you can create actions where a change to a detail record updates a field on the related main record. Cross-object field updates work for custom-to-custom master-detail relationships, custom-to-standard master-detail relationships, and a few standard-to-standard master-detail relationships. products: - Flow Builder - Salesforce Platform release: "264" --- # Cross-Object Field Updates For all custom objects and some standard objects, you can create actions where a change to a detail record updates a field on the related main record. Cross-object field updates work for custom-to-custom master-detail relationships, custom-to-standard master-detail relationships, and a few standard-to-standard master-detail relationships. ### Required Editions ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) Note Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
Available in: Lightning Experience and Salesforce Classic
Available in: Enterprise, Performance, Unlimited, and Developer Editions
For example, in a custom recruiting application, create a workflow rule that sets the status of an application (the main object) to “Closed” when a candidate (the detail object) accepts the job. Or, for standard objects, create a rule to change the status of a case from “Awaiting Customer Response” to “In Progress” when a customer adds a case comment. ## Custom Object to Custom Object Cross-object field updates are supported for all custom objects that are children of custom objects in a master-detail relationship. ## Custom Object to Standard Object Cross-object field updates are supported for custom objects that are children of certain standard objects in a master-detail relationship. The standard objects that support cross-object field updates from custom objects are: - Account - Asset - Campaign - Case - Contact - Contract - Contract Line Item - Entitlement - Opportunity - Order - Question - Quote - Service Contract - Solution ## Standard Object to Standard Object Cross-object field updates are supported for standard objects that are children of standard objects in a master-detail relationship. However, only these standard-to-standard relationships are supported. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) Note If you have workflow rules on converted leads and want to use cross-object field updates on the resulting accounts and opportunities, you must enable the lead setting Require Validation for Converted Leads. - Case Comments updating Case - Email updating Case ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_tip.png) Tip To create workflow rules so that case comments or emails automatically update fields on associated cases, select **Case Comment** or **Email Message** in the Object dropdown list when creating a workflow rule and select **Case**in the Field to Update list. Email-to-Case or On-Demand Email-to-Case must be enabled for your organization to use the Email Message in a workflow rule. - Opportunity Product updating Opportunity ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) Note Cross-object field updates to a parent opportunity's Amount and Quantity fields only work if the opportunity has no opportunity products associated with it. - Opportunity updating Account—Supported for both business accounts and person accounts. Standard-to-standard cross-object field update actions: - Can’t be used in, or assigned to, approval processes. - Update a parent record even if the user doesn’t have edit access to it. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) Note If you have Apex code that updates parent fields in the same relationships as a cross-object field update action, consider replacing your code with cross-object field updates. Otherwise, both will fire, and since workflow rules run after Apex triggers, the workflow field update will override any change made by your Apex code. #### See Also - [Considerations for Field Update Actions](https://help.salesforce.com/s/articleView?id=platform.workflow_field_update_considerations.htm&release=264.0.0&type=5 "Learn how to use field update actions to their full potential in workflow.") - [Object Relationships Overview](https://help.salesforce.com/s/articleView?id=platform.overview_of_custom_object_relationships.htm&language=en_US)