Ideas

Having the source/reason attributes set to dynamic chat for the  updates made by dynamic chat will help us filter on the field values updated specifically by the dynamic chat in the SL/triggers. Currently the source in the field updates made by dynamicChat in activity shows Web Service API, it’d be great if we could say if the values were updated by the dynamicChat  specifically. Additionally, it'd also be great if dynamic chat is added as one of the input sources that we could check-mark to block updates in the field management section on the respective fields, if need be. There could be use-cases where we would wanna capture the data from dynamic chat for a new person but not update if there's already a non-empty value present on an existing person in the Marketo.   ... View more