Total Rows Incorrect from Salesforce report

I have a data set that pulls from a Salesforce report with Accounts, Contracts, and Subscriptions. I'm using the FULL ID (18-digit) on the Subscription record as the unique ID to pull more than 2000 records from Salesforce.

 

When I refresh that data set, I get wildly varying records returned, sometimes over the number of records I see in Salesforce, sometimes under... by a couple thousand each time.

 

When I look at the data table for that data set in Domo, I do see duplicate IDs in the FULL ID column. I exported the same report from Salesforce and verified that there are no duplicates for that column in Excel.

 

Has anyone run into this before?

Best Answer

  • robertc
    robertc Member
    Answer ✓

    I found a solution for my issue. Instead of using the 18-digit FULL ID for the subscription record, I used Subscription # (which is also unique) and now I have the right number of records.

Answers

  • Hi @robertc 

     

    This might be a silly question but in the connector settings are doing an append or replace of the records ?

     

    if you are doing an append, you can look at the last batch id or batch last run date to differenciate each pull

    Domo Arigato!

    **Say 'Thanks' by clicking the thumbs up in the post that helped you.
    **Please mark the post that solves your problem as 'Accepted Solution'
  • Good question. I'm doing a replace. I also have another user who created his own data set with the same settings against the same report, but using his SFDC credentials and he gets the same result... varying row count and duplicates. He's also using the Replace method.

  • guitarhero23
    guitarhero23 Contributor

    Sounds odd. If you don't figure it out and you're able to I'd recommend using SOQL (workbench would help write it https://workbench.developerforce.com/login.php) to create the same filters that are on your report and use "Query" as the how to select in the Salesforce connector settings. I've had no issues with this.



    **Make sure to like any users posts that helped you and accept the ones who solved your issue.**
  • @robertc Would you mind sharing a screenshot of your Domo settings for this dataset?


    “There is a superhero in all of us, we just need the courage to put on the cape.” -Superman
  • Screen Shot 2019-07-02 at 10.46.06 AM.pngScreen Shot 2019-07-02 at 10.46.18 AM.png

  • robertc
    robertc Member
    Answer ✓

    I found a solution for my issue. Instead of using the 18-digit FULL ID for the subscription record, I used Subscription # (which is also unique) and now I have the right number of records.