Wednesday, December 19, 2012

Cross-Object Workflow in

With Spring '12 release, cross-object field update in workflow rules and approval processes is now support standard objects. Both custom-to-standard and limited standard-to-standard relationships are supported. This feature only available in Enterprise and Unlimited edition.

Only Master-Detail relationship support for cross-object workflow, so it is not for objects with Lookup relationship.

Here is a sample case of using Cross-Object workflow.
Master object: Customer__c
Child object: Order__c
Company would like to know how total amount and when latest order for each customer, use payment date instead of order date. Payment date will be blank when customer have not make payment.

Here we go:
1. Create a workflow in Order 
Evaluation Criteria : Evaluate the rule when a record is created, and every time it’s edited
Rule Criteria:
NOT ISBLANK( Payment_Date__c ) && 
( Payment_Date__c >= Customer__r.Payment_Date_hidden__c || 
ISBLANK( Customer__r.Payment_Date_hidden__c ))

- if Payment Date in order is blank, stop workflow
- if Payment Date in order is newer than stored Payment Date in customer, proceed workflow OR if stored
Payment Date in customer is blank

2. Create a field update action in Order
Update Payment Date in Customer
Select object = Order
Field to Update = Customer, the select field Payment Date
Formula Value = Payment_Date__c from Order

3. Create a Roll-Up Summary field in Customer for Total Amount
Create new Roll-Up Summary field from Customer object
Summarized Object = Orders
Select Roll-Up Type = SUM
Field to Aggregate = Amount
Filter Criteria = Payment Date NOT EQUAL TO blank

Last one, remember to Activate the workflow.

If you see in above process, workflow in Order will update field in the parent object Customer. So, it is cross-object workflow field-update.

The same solution you can use to update Account from Opportunity, example: if opportunity is Closed Won, automatically update Account Type to Customer.

For more information and standard objects supported, see this release document and find section Cross-Object Workflow. 


  1. Only custom-to-standard and limited standard-to-standard relationships are supported. Your example is invalid since both are custom objects, isn't it?

    1. Carmen, we can have Master-Detail relationship between custom-custom object. See screenshot:
      Object1 is parent and Object2 is detail, both are custom object and linked with Master-Detail relationship.
      Hope this clear and help.

  2. I want to use this for contracts and accounts, but can you explain a little further your hidden fields you are using?

    1. Heidi,
      1. Account - Contract relationship do not support cross-object workflow, only Opportunity supported from Account for standard
      object. That is why I said "limited standard-to-standard relationships are supported"

      2. It is just sample using 'Payment_Date_hidden__c', it can be any field.


Page-level ad