Optional flag in API calls to ignore trigger qualification | Community
Skip to main content
Jonathan_Wu
Level 3
September 15, 2016
New

Optional flag in API calls to ignore trigger qualification

  • September 15, 2016
  • 3 replies
  • 2751 views

Should at least apply to importlead if not other REST API endpoints too, but an optional flag for ignoreTriggers would allow for a mass data update and give a customer an option to ignore qualifications to Trigger Campaigns.

Use case: a data fixup via REST importLead would have a primary purpose of reconciling data/fixing data that was accidentally changed, but changing it again could result in trigger and/or campaign processing backlogs when these aren't really meant to be new values and just reverting back to older values.

3 replies

Jonathan_Wu
Level 3
September 16, 2016

activity log items would probably need to indicate that ignoretrigger was set to true or something

May 10, 2017

This feature would be extremely helpful when executing a bulk process to consolidate duplicate records.  We run periodic deduping in SFDC and allow the SFDC to Marketo sync to update and consolidate in Marketo.  When you perform this consolidation the smart campaign triggers execute which can send communications, alert notification to Sales Reps for example. 

February 6, 2020
No text available