Copy multiselect dropdown values using process definition update field event

Hi All,

I have same multiselect dropdown in document and opportunity with below values and when user create record from document module subpanel in  opportunity  record view then I want to copy the same values to opportunity module using process definition:

  • Choice 1
  • Choice 2
  • Choice 3

Case 1:If user select

  • Choice 1  then update Choice 1 in multiselect dropdown of opportunity

Case 2:If user select

  • Choice 2  then update Choice 2 in multiselect dropdown of opportunity

Case 3:If user select

  • Choice 3  then update Choice 3 in multiselect dropdown of opportunity

Case 4:If user select

  • Choice 1 & Choice 2  then update Choice 1 & Choice 2 in multiselect dropdown of opportunity

Case 5:If user select

  • Choice 2 & Choice 3  then update Choice 2 & Choice 3 in multiselect dropdown of opportunity

Case 6:If user select

  • Choice 1 & Choice 3  then update Choice 1 & Choice 3 in multiselect dropdown of opportunity

 

How to achieve above using process definition update field event. 

Kindest Regards,
Shreya

  • Hi ,

    SugarBPM does not provide a dynamic way of performing this update. You would need to have a gateway that evaluates for every possible combination of selections in the multiselect field and based on the combination of options identified, it sets the parent opportunity field the same exact options. That design is very heavy on maintenance and also gets unwieldy very fast as it is a factorial function (e.g. 4 multiselect options means 24 different possible combinations, 5 multiselect options is 120 combinations, etc.). 

    The other potential complexity is that you are looking to copy values up to the parent record. Since you indicate the documents are created from the subpanel, it's possible more than one document could be related to the opportunity. SugarBPM would not be well-suited to handling conflicts where different documents have different options selected and you want to retain all selected options. 

    My recommendation is that this would be best suited by using a custom logic hook rather than SugarBPM as you can account for both of the above scenarios much easier than you would through SugarBPM.

    Chris