Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago

Salesforce Object connector - API calls per Objects ?

Hi,

 

A question related to the standard connector given by Power BI to connect to 'Salesforce Objects' highlighted below.

 

 

I came to know that salesforce has some limitations in the number of API calls that can be made over a period of time.

 

Can someone throw light around this, if we use the highlighted standard connector to connect to Salesforce objects, Will the system make one API call per Salesforce Object or how does that work in background with respect to the API calls ?

 

 

Mvh,

Kesavan.

 

Need Help

5 Replies

  • lbendlin's avatar
    lbendlin
    Super User
    6 years ago

    Talk to your company's SFDC admin, they can show you exactly how many calls you are consuming. The object calls are usually batched at 500 rows per batch.

     

    Make sure you know the cardinality of your objects. The opportunity object for example can have millions of rows depending on your company size, and this can really drag you down in reporting, and can eat through your API call allocation in no time.

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      Hi lbendlin ,

       

      Do you mean 1batch would be 1API request ? and 1API request can fetch max. 500 records from Salesfoce ?

       

       

      Mvh,

      Kesavan.

      • lbendlin's avatar
        lbendlin
        Super User
        6 years ago

        That's my understanding. Ask your SFDC admin. Might be 1000 per batch.

  • metrica's avatar
    metrica
    Post Prodigy
    3 months ago

    Hi kesavan,

     

    Here's how API calls break down with the native Salesforce Objects connector for your scenario:

    Initial connect:

    • 1 call for the object catalog (/sobjects/)
    • Describe calls for the objects you select to fetch their schema (typically cached for some time)

    Per refresh:

    • 1 SOQL query call per object (/query?q=SELECT...)
    • The REST API returns up to 2,000 records per response (or 1 MB, whichever comes first), so larger result sets require paginated queryMore calls
    • If you use CreateNavigationProperties=true and expand related tables in Power Query, each relationship expansion adds extra API calls per parent record - on large objects with multiple expansions, this can dramatically inflate your call count

    Salesforce daily API quotas vary by edition (Enterprise gets ~100K/24h base plus per-user allocations, Performance/Unlimited get much more), but heavy Power BI refreshes with relationship expansion can still chew through your headroom quickly.

     

    The way to keep your API consumption predictable is server-side filtering - filter and select columns on the Salesforce side before data leaves your org. Power BI Connector for Salesforce on AppExchange does this in a UI inside Salesforce, so you only pull the rows and columns you actually need.

     

    Free 30-day trial if you'd like to test it on your specific objects. Details at https://metricasoftware.com/, demo available on request.

     

    Cheers,

    Metrica Team.