When one of our clients enters a campaign, we would like to send an alert out to their opportunity owner. This client could easily have multiple opportunities with different owners for each (in MS Dynamics). To combat sending an alert to the wrong owner, we want to reference the most recent. Originally we had planned to do this with a velocity script in the alert flow step, however we recently learned that is not possible.
We would rather not have to synch these fields down from CRM into marketo on the lead level. Is it possible instead to reference a custom object that contained the current opportunity owner's email address? Or would we run into the same issue as before (not sure if a custom object syncs info over to a lead level field which we can then reference, or if a custom object can populate information on the alert send-to without needing any scripting).
Originally we had planned to do this with a velocity script in the alert flow step, however we recently learned that is not possible.
Is it that the velocity script cannot work in an alert email or is this that it's impossible for the velocity script to reference the opportunity object (which would see really weird to me)?
Can the velocity script see the most recently updated Open Opp details? Or see Custom Objects? That should solve it.
By and large the velocity scripting has worked as intended within emails (it can reference the most recent opportunity, different types of opportunities, etc.) The problem is that ideally we would like to reference the opportunity owner in a flow step - however to my knowledge you cannot run a velocity script in a flow step (unlike a lead level token which you can).
We were wondering if it is possible to reference a custom object in the flow step, or if the same processing limits apply to custom objects in flow steps as well.
No, Velocity scripts can only run from within an email, nowhere else.
You could solve the issue in SFDC, with an account field and a workflow on the opportunity. The workflow will copy the opportunity owner data to the account each time the opportunity is created and or updated. This account field being mapped to Marketo, you will be able to use this data as tokens.
If you really want to make sure that it's always the most recent opportunity, you will need to use triggers in SFDC to do the same thing. The trigger will be able to really make sure that it is triggered only on the most recent opportunity.