Salesforce Leads - Trigger Owner Re-assignment from Marketo

[haliddelkic]

Dear Marketo community,

Does anyone know if it’s possible to trigger Lead Owner re-assignment of an existing Salesforce lead using Marketo? And if so, how?

My Scenario

We’re exploring options to sync all Marketo records to SFDC, including pre-MQLs. 

Pre-MQLs currently exist in the Marketo environment only. 

The rationale is to assign pre-MQLs to the Marketo Sync SFDC user profile during the initial sync.

Once a lead qualifies as an MQL, lead ownership should re-assign to the relevant salesperson according to the active Salesforce assignment rules.

Already tried...

..the Change Owner flow step. However this option forces you to select a specific named SFDC user.

While this is the obvious option, I'm curious if there are any workaround possibilities where we don't need to re-build the same assignment rules in Marketo that already exist in Salesforce. 

I also did a test on an existing lead record using the Sync Person to SFDC flow step with “Use Auto-Assignment Rules” but didn’t really expect this to work. And it didn't. 

Any thoughts, ideas, comments…chuck them my way.

Thanks in advance. 

[Michael_Florin]

I guess this depends on your Salesforce setup, but we for instance need to set the field "RunAssignmentRules" to TRUE in order to have Salesforce's assignment rules kick in.

[Salytics]

We've solved this issue by tackling things from the Salesforce side.  It can be done using apex as follows:

1. Trigger approach:
   Within the lead trigger/handler, isolate leads that are being updated to meet criteria (probably just lifecycle stage = MQL + current owner = Marketo Sync for your use case).  For these leads, push them through an update after setting
   

   Database.DMLOptions dmo = new Database.DMLOptions();
   dmo.assignmentRuleHeader.useDefaultRule = true;​

2. Process builder approach:
   Use this if you want the ability to turn off or configure the entry criteria.  The PB flow can be configured to detect the MQL change criteria, then push the leads to an invocable apex method that causes the leads to update using DML options assignmentRuleHeader (basically the same code in the trigger approach)