Leads Not Syncing with MS Dynamics During Workspace Upload | Community
Skip to main content
michellechopin
michellechopin
Community Manager
March 28, 2022
Question

Leads Not Syncing with MS Dynamics During Workspace Upload

  • March 28, 2022
  • 2 replies
  • 5380 views

Hi Community Members!

 

This is my first time working in an organization that uses Workspaces and Partitions (yay for getting to experience more of Marketo!). I'm currently testing an upload process ahead of a large list import (into one of our newest workspaces/partitions) to make sure everything works properly and am encountering this variety of issues (we use MS Dynamics for CRM):

 

  • Lead A : Brand new to Marketo and Dynamics, uploaded via Workspace 3 - ended up in Default Workspace AND Workspace 3, synced to Dynamics with appropriate field information but no data in the Marketo Activity log
  • Lead B : Brand new to Marketo and Dynamics, uploaded via Workspace 3 - ended up in Default Workspace AND Workspace 3, did not sync to Dynamics and no data in the Marketo Activity log
  • Lead C : I don't think this existed in Marketo prior, but existed in Dynamics, uploaded via Workspace 3 - ended up in Default Workspace AND Workspace 3, did not update in Dynamics with appropriate fields, and no data in the Marketo Activity log
  • Lead D : Exists in Marketo, does not exist in Dynamics, added via Workspace 3 - received an error noting this lead already existed in another (Default) partition, did not sync to Dynamics (expected as campaign is in Workspace 3 and required leads to be on the import list)

I checked our Workspace/Partition set up and two Workspaces are associated with two Partitions (not including a screenshot of the settings for privacy reasons but re-created as a table with dummy data to demonstrate):

Partition Name Workspaces
Default Default, Workspace 2
Workspace 2 Workspace 2
Workspace 3 Default, Workspace 3

 

I am wondering if this explains why leads are being uploaded to two workspaces at import and, if so, whether that would cause the sync to MS Dynamics to fail or ignore the lead completely because of that duplication across workspaces. The only caveat here is that Lead B, which matches the criteria for Lead A didn't sync to Dynamics at all - not being able to see the Activity log makes this really hard to troubleshoot!

 

If anyone has any insight, it would be much appreciated. We can potentially change the settings but wanted to get an idea if this was the problem before doing that (I also have a ticket in with Support so they can dig into the leads/data specifically).

 

Many thanks as always for any help provided  😀

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Katja_Keesom
Katja_Keesom
Community Manager
March 29, 2022

Hi Michelle,

I would like to double check something here. As Darshil mentions, typically a single record in a list is only created once and that can be in one partition only. The fact that you received an error message on that last lead confirms to me that your instance is not altered on that front. How did you deduce the leads were created in two partitions? You should be able to see them from both workspace 3 and the default workspace, but I expect they only exist in the single partition. As you can see leads across both partitions from the default workspace, I suspect you are seeing the same lead twice. You can confirm this by adding the Person Partition field to your view. If I am right, you will see those leads, but they will show (even when viewing from the default workspace) that they are created in partition 3.

 

And Darshil is absolutely right, the leads will not automatically be pushed to MSD unless you tell Marketo to.

 

Kind regards,

Katja

Darshil_Shah1
Darshil_Shah1
Community Manager
March 29, 2022

Thank you, @katja_keesom !

 

@michellechopin, you may already know this but FYR - the correct way to check in which partition a person belongs to is by checking the system managed Person Partition field on the person profile page's info tab, this field can also be pulled in to the person list view as Katja mentioned. 🙂

    michellechopin
    michellechopinAuthor
    Community Manager
    March 31, 2022

    Hi @darshil_shah1 and @katja_keesom,

     

    Firstly, thank you both for jumping in here - I very much appreciate your insight and questions, which have helped me better understand. I had thoroughly confused myself as to Workspace vs Partition and after re-reading this article plus your comments, now it is much more clear.

     

    Two updates based on each of your comments/replies:

     

    1. I assumed these leads were in both partitions because when I searched within the Database while in each workspace, the leads always came up. However, upon looking closer at the specific lead examples I sent Marketo support, I can see the snippet at the end of each lead's URL showing either accessZoneId=1 (the lead that was in the Default partition and gave an error) or accessZoneId=2 (the test leads I had successfully imported). I also took at look at the Campaign Members in the smart campaign I ran and added the Person Partition column to the view - they are absolutely only in one partition (so this is definitely a user error of understanding on my part 😋). I can also confirm this by going into each lead specifically to look up the field.
    2. In the Flow for this particular import, I have Sync Person to Dynamics ahead of other data updates we do on this campaign:

     

    Notes:

    • There no Results in the Smart Campaign - it shows "No activities found"
    • When I go into the Campaign Members, and choose Qualified People, there's nothing there either. 
    • Each of the leads that didn't make it through to Dynamics also shows nothing in the Microsoft Type field on the lead record

    So, while the leads are definitely going into the right place in Marketo, I need them to sync to Dynamics and cannot for the life of me figure out what is missing/going wrong. Is there anything else I could check or look into to see if I can gather some more information?

     

    I am going to try a couple more test leads now as I just saw that we updated our Marketo/Dynamics integration so perhaps that was causing the issue. Will update if anything works when I do that!


    Thank you again  😀

    Michelle

     

     

     

    Darshil_Shah1
    Darshil_Shah1
    Community Manager
    March 29, 2022

    Interesting, so you're saying that leads are getting created in more than one person partition even though imported once in a WS!

    A person can only exist in a single person partition OOTB (there are ways to change the dedupe criteria from just the email address to a compound key so that leads with same email address can co-exist in multiple person partition, but story for another day).

     

    When a person is created from a WS that can access more than one person partitions, by default the person gets created in the WS's primary person partition only (i.e., it should not get created in all the person partition like in your case)! FYR, primary person partition for each WS is indicated by a * <asterisk> next to the partition name in the Admin > Workspace and Partition > Workspaces. It is noteworthy that this person can be accessed and seen by and from all the WSes that can see this partition.

    Also, logic to route people to different person partitions can be setup in the Assignment Rules in the Admin > Workspace and Partition  > Person Partition > Assignment Rules and alternatively, routing campaigns can also help change the person partitions - do you have of those setup?

     

    As a good practice I usually have the Default WS access all the person partitions - so that I can have all the leads at one place if need be for pulling up data/SL, etc., rest of the WS can then selectively access Default and/or other respective partitions!

     

    Lastly, do you have campaigns that listens for new people getting created and push them into the CRM? New leads that enter into Marketo do not get created in CRM automatically.

     

    Terms & ConditionsAccessibility statement

    Loading footer...