Can I mass export "Sync error" data or upload to Salesforce?

Comments

4 comments

  • Avatar
    Darcy Groom

    Hey Alex, my answer is long-winded, but I think this should cover all the bases.

    My recommendation would be to export all your people data, rather than just these sync logs. Exporting the sync logs is one matter, but then you'd need an export of the data on those people records to efficiently upload into Salesforce. Exporting all your people data will quickly tell you whether or not they're linked to Salesforce and give you the data you need to upload them all in one fell swoop. 

    If you go to the People tab, set the widest possible filters, then select Export People under the People Actions dropdown, this will email you a csv file of all people. That file will include a column with the header "CRM ID". If that column is blank, that's an immediate indicator that those people do not have an associated record in Salesforce. You can quickly filter out anyone with a linked Salesforce record, then modify the spreadsheet for your import to SFDC.

    Long term, I would recommend setting up an automation rule to prevent these sync errors moving forward. You could set up something like the following. The "is not null" criteria help you ensure any fields required by Salesforce are populated before attempting to create a record.

     

    Let me know if that works for you!

    Also for reference, the Support Team can sometimes help pull an export of the Activity Sync errors if you open a ticket with them. I do think it would be a good product request to be able to export these directly from the application yourself. You can use the question mark icon in the upper right hand corner to pull up the Submit Feedback form in-app.

     

    0
    Comment actions Permalink
  • Avatar
    Sean Richards

    Hi Darcy,

    What are the benefits to allowing people to be created in Salesloft and then sync'd to SF, vs training people to create all people in SF, then sync them to SL when they want to start working them? We have a really strict process to bring new people into our tech stack to prevent duplicates and thus, allowing people to create dupes via this proposed solution would open up many other issues for us? Keen to know your thoughts?

    0
    Comment actions Permalink
  • Avatar
    Darcy Groom

    Hey Sean - that's a really good point. What you suggested would actually be best practice. Salesforce should always be the record of truth and I would typically recommend creating leads/contacts there first. Ideally, the automation rule I suggested doesn't have to ever come into play. But by having a rule like this active, it acts as a fail-safe, so in the instance that a new record is created in SalesLoft first, SalesLoft can attempt to push that over into Salesforce. 

    Keep in mind the SalesLoft sync works in such a way that if a Person is created in SalesLoft, it will first scan Salesforce for leads/contacts that match that email address (order of which object it checks or checks first is dependent on your settings). Only if a matching record is not found will this rule come into play.

    0
    Comment actions Permalink
  • Avatar
    Sean Richards

    Thanks for the response Darcy.

    0
    Comment actions Permalink

Please sign in to leave a comment.