ShannonKelly1

Hi @PaddyRR , I think Darshil's response here might be helpful to you. He references Sandy's blog post Sorting objects and lists in Velocity.

Yes, that would take care of it if those are the only smart campaigns that are syncing those records. Just remove the flow step.

I am not sure exactly how your smart list was formatted, but try:

Hi @HoaPhan199 , it is unclear if the custom sync filter can be employed to restrict Opportunities from sync in Salesforce-Marketo integrations, as it can for Dynamics-Marketo integrations. (Related: for some reason the sync filter is not even documented for Salesforce integrations in the Marketo Pr...

Yes, if you have a local smart campaign within your program with a Sync Person to Microsoft flow step for members of that program only, remove that flow step.You may have other smart campaigns in your instance with Sync Person to Microsoft flow steps that are "global" -- for instance, the campaign m...

It was my understanding that the Marketo-SFDC integration required that the Sync User has the typical permissions for the Opportunity object, even if you do not intend to sync opportunities. To control the sync of Opportunities, you could employ a custom sync filter field on the records in that obje...

Are the SFDC Campaigns synced with Marketo Programs?Create an Executable smart campaign with CDV flow steps for the fields you want to update, and use the {{program.name}} token (assuming your Marketo programs share a naming convention with the SFDC campaigns).In the Marketo programs where the SFDC ...

Hi @Jay00031987 , Agreeing with @Michael_Florin . One callout: Since your Marketo instance already has a native integration in place with Salesforce, the Opportunity API is available as read-only (not write). When integrating the second CRM, you will likely have to create custom objects to replicate...

Good work, @neelambakre ! A couple of callouts: Beware of Channel bloat. It appears that you are tracking a significant interaction in this channel, so it makes sense to create a new channel for it, but avoid creating new channels per program or initiative. Try to keep the Channels and program membe...

Hi @neelambakre ,Darshil and Sanford make good points here. Rather than using "Change Program Success" as the flow step, you could consider Change Program Member Status . That way, you will see the progression of people through the program statuses as they interact with your program, rather than jus...