Thursday, Oct. 19, 2017

Update Child BC Field based on Parent BC Field using Data Validation Manager(DVM)

Written By:

|

November 12, 2012

|

Posted In:

Requirement:

The requirement is to update a child BC field when a Parent BC field is updated on the UI i.e. there is a field called ‘Priority’ in Opportunity (Parent BC) and Action (Child BC)which have values as
Parent BC – Opportunity BC field Priority has values as 1, 2, 3.
Child BC – Action BC field Priority has values as 1-ASAP, 2-High, 3-Medium.
When the user sets the Priority field in Opportunity BC as “1” and saves the record, the corresponding Child BC Action record field Priority must be updated to “1-ASAP”.
Similarly,
When the user sets the Priority field in Opportunity BC as “2” and saves the record, the corresponding Child BC Action record field Priority must be updated to “2-High”.
When the user sets the Priority field in Opportunity BC as “3” and saves the record, the corresponding Child BC Action record field Priority must be updated to “3-Medium”.

Solution:
The above requirement can be implemented using Data Validation Manager (DVM) and Runtime Events. Follow the below configuration steps in your client application.
1. Open your client application and go to Sitemap->Administration-Data Validation->Rule Sets. Create a New record as shown in screenshot below:

DVM1

Save the record.

2. Click on the hyperlink in the Name field and create 3 Rulesets as shown in screenshot below

DVM2

ParentFieldValue(“Priority”) = refers to Priority Field in the Opportunity BC. Link Spec property for this Field in Opportunity BC is set to FALSE.

For each Rule set ensure that the following flags are set as shown below in the bottom applet (Tab – Rule Detail)

DVM3

3. Now for the first RuleSet, click on Actions Tab below and create the following records as shown below:

DVM4

Similarly for the second rule set, create records in Actions Tab as below:

DVM5

Similarly for the third  rule set, create records in Actions Tab as below:

DVM6

4. Finally Activate the rule set by clicking on Activate button

5. Next step is to create Run time events to trigger the above DVM rulesets.

Go to Sitemap->Administration- RunTimeEvents-> ActionSets and create a new record based on Business Service Type as below

Name it as “Update Opty_Activity Action”

DVM7

Business Service Name = Data Validation Manager

Business Service Method= Validate

Business Service Context = “Rule Set Name” , “Update Opty_Activity”

Go to Sitemap->Administration- RunTimeEvents-> Events and create a new record as shown in screenshot below

DVM8

In the end, press the menu button and click Reload Runtime events.

6. Now when you change the Priority field in Opportunity BC to “1” and save the record, the Activity highlighted below would have its Priority field set to “1-ASAP”.

Similarly, “2” in Opportunity BC field Priority will set Action BC Priority to “2-High”



Share This Article

About Author

Gurdeep

Hi, I am sharing my experience to alleviate beginners with open UI and HI version of Siebel CRM. I work in Sun Life Financials and can be reached via IT Tool box as well. Thanks.

  • http://profile.yahoo.com/46I4ZWQJVSFCYORUEWBICIMLXU ranji

    Does the StoponError flag have to be checked ? And what rulemessage should be entered ? Looks like its mandatory.

    • Gurdeep

      Hi Ranji, yes the Stop on Error flag has to be checked. For the rule message you can create a dummy message in Validation Messages tab.

  • Sarah B.

    Hi Gurdeep, I don’t get why the use of expression ParentFieldValue(“Priority”) “1”, and so on for “2” and “3”.
    ParentFieldValue(“Priority”) returns value “Priority”. What does this have to do with Opty Priority value? Can you explain? Thanks.

  • Aki

    Thanks. It helps. Nice article.