What is the "reason" constraint supposed to contain in a "Data Value Changes" trigger ? | Community
Skip to main content
A
Anonymous
May 16, 2018
Solved

What is the "reason" constraint supposed to contain in a "Data Value Changes" trigger ?

  • May 16, 2018
  • 1 reply
  • 5057 views

The picklists come up empty for both "source" and "reason" in the Data Value Changes constraint. This thread started by @Grégoire Michel discusses the same thing but focuses on the "source" constraint - and concludes that the list of acceptable values are the same as those for the Source Type (such as in the "Person is Created" trigger) - and that those values are documented here: Understanding System Managed Fields - Marketo Docs - Product Documentation

Does anyone know what the reason constraint is supposed to contain?

Its seems like these two constraints could be useful for documenting the source for GDPR (or CASL) opt-in.

Thank you!

Denise

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Grégoire_Miche2

Hi Denise,

some examples of DVC Reasons, extracted from a live instance:

​

SourceReason
sfdcSynched from salesforce.com Account ID XXXX
sfdcSynched from salesforce.com Contact ID XXXX
sfdcSynched from salesforce.com Lead ID  XXXX
Web form filloutForm fill-out, URL: XXX
N/AChanged by Smart Campaign XXX action Change Data Value

-Greg

1 reply

Grégoire_Miche2
Grégoire_Miche2Accepted solution
Level 10
May 16, 2018

Hi Denise,

some examples of DVC Reasons, extracted from a live instance:

​

SourceReason
sfdcSynched from salesforce.com Account ID XXXX
sfdcSynched from salesforce.com Contact ID XXXX
sfdcSynched from salesforce.com Lead ID  XXXX
Web form filloutForm fill-out, URL: XXX
N/AChanged by Smart Campaign XXX action Change Data Value

-Greg

    Denise_Greenb12
    Denise_Greenb12
    Level 6
    May 17, 2018

    Hi Greg,

    Thank you! Silly me - I realized after I posted the question that I could just look in the activity log. It's frustrating to me that you can't access the values in the "source" and "reason" constraints in the flow. For example, with GDPR and CASL in mind, wouldn't it be useful to have a token for DVC reason that could be copied into a field? E.g., DVC Changes->Opt-In->New Value=True. Flow: copy value from DVC reason into an Opt-In Source field.

    - Denise

    Grégoire_Miche2
    Grégoire_Miche2
    Level 10
    May 17, 2018

    Hi Denise,

    Pretty easy to create your own custom field to handle this info.

    -Greg

    Terms & ConditionsAccessibility statement

    Loading footer...