Finding the best Salesforce Power BI connector is not as straightforward as it looks. Most teams start with Power BI’s built-in options, hit real limitations, and then go looking for something better.
This review covers what those limitations are, what to look for in a third-party connector, and why Power BI Connector for Salesforce stands out as the most complete solution currently available on the Salesforce AppExchange.
Why the Search for a Better Power BI Salesforce Connector Begins?
Power BI ships with two native Power BI Salesforce connectors. Both are free. Both work for simple scenarios. Neither is designed for serious, production-grade reporting.
The Salesforce Reports connector is the most common starting point. It connects to Salesforce reports via the Analytics API and requires zero data modeling knowledge. The limitation is the 2,000-row cap enforced by the Salesforce Reports API. Hit that limit and Power BI silently returns incomplete data — with no error, no warning, and no way to know unless you manually check record counts against Salesforce totals.
The Salesforce Objects connector is the more capable of the two. It bypasses the Reports layer entirely, querying objects directly with no row limit. In practice, it creates a different set of problems: no server-side filtering (entire objects load into Power BI memory before any scoping occurs), authentication failures from OAuth session conflicts, field count limits per query, and INVALID_QUERY_LOCATOR errors when concurrent refreshes exhaust the shared Salesforce API quota. It also only supports Import Mode — no DirectQuery, no live data.
For teams managing serious data volumes, multiple users, or any kind of governance requirement, both connectors fall short. This is the gap that third-party solutions fill.
What Makes a Good Salesforce Power BI Connector?
Before evaluating any specific tool, it helps to define what a proper Power BI Salesforce connector should do:
- No row limits. The connector should query Salesforce objects directly without record caps.
- Server-side filtering. Data should be scoped before it reaches Power BI, not after. This is the difference between transferring what you need and loading everything then filtering locally.
- Salesforce-native architecture. A connector that operates inside Salesforce — rather than connecting from an external server — keeps data within your existing security perimeter and eliminates third-party data handling concerns.
- Centralized governance. In team environments, every analyst should not be building and maintaining their own independent connection. The connector should support shared, reusable configurations.
- Incremental refresh support. Large datasets that grow continuously need a way to refresh efficiently. Loading millions of records on every cycle is neither fast nor API-efficient.
- Access control aligned with Salesforce permissions. Users should see exactly what their Salesforce profile allows — no more, no less — without any separate permission configuration inside the connector.
Power BI Connector for Salesforce: A Practical Review
Power BI Connector for Salesforce by Metrica meets all of those criteria. Here is a detailed look at how it performs across each dimension.
Architecture: Truly Salesforce-Native
Power BI Connector for Salesforce installs inside your Salesforce org as a managed Salesforce AppExchange package.
It is not an external tool that connects to Salesforce from outside — it operates within your Salesforce environment. Power BI connects to an OData endpoint hosted on a Salesforce Site that you configure during setup.
This architecture means data does not pass through any third-party infrastructure. It goes directly from Salesforce to Power BI.
For organizations with data residency requirements or strict security policies, this is a meaningful differentiator compared to ETL-based alternatives that stage data in intermediate cloud storage.
Data Sources: The Core Concept
The central concept of the Power BI Connector for Salesforce is the data source — a saved configuration that defines which Salesforce objects, fields, and filter conditions to export. Configuration happens inside Salesforce, not in Power BI. By the time Power BI connects, the Salesforce data is already scoped.
This is architecturally different from native Power BI Salesforce connectors, where all configuration (object selection, field choices, filtering) happens in Power Query after data is already loaded. With Power BI Connector for Salesforce, the Salesforce side does the work. Power BI receives exactly what was defined.
There are no limits on how many data sources you can create. A sales team gets their own pipeline data source, support gets a case and ticket data source, marketing gets leads and campaigns – each scoped to the objects and fields that team actually uses.
Data sources can be shared across users within each team, so one well-configured definition serves everyone. No duplicate configurations, no conflicting field selections, no analysts independently deciding what “active opportunity” means.
Performance: Server-Side Filtering and Incremental Refresh
Two features directly address the performance problems of native Power BI Salesforce connectors.
Server-side filtering means filter conditions (date ranges, record owners, statuses, record types) are applied in Salesforce before any data is transferred. Native Salesforce connectors load entire objects into Power BI memory and filter locally, consuming API quota and local memory regardless of how little data you actually need. With Power BI Connector for Salesforce, only matching records travel across the connection.
Incremental refresh loads only new or changed records on each refresh cycle instead of reloading the full dataset. For objects like Opportunities, Cases, and Activity records that accumulate millions of rows over time, incremental refresh is the difference between a five-minute refresh and one that times out. Power BI Connector for Salesforce uses an OData-based approach with explicit DateTime zone handling to make incremental refresh work correctly with Salesforce’s date field types.
Features: Power BI Connector for Salesforce
No row limits. Every data source exports in full, regardless of record count.
SOQL query mode. Beyond the visual configuration interface with basic filters, power users can write SOQL queries directly for complex filter logic, relationship navigation, and precise field selection.
Entity Relationship Diagram. Power BI Connector for Salesforce includes a visual ERD that shows how your selected objects relate before you save a data source. This prevents incorrectly structured Power BI data models – a common problem when mapping Salesforce’s complex schema manually.
Access tokens with expiry and revocation. Each user authenticates with their own token, scoped to their Salesforce permissions. Tokens support expiry dates and can be revoked immediately. Combined with audit history logging of every data source change, this gives compliance teams a clear picture of what data is flowing where and who configured it.
Agentforce integration. A notable addition for teams using Salesforce Agentforce: describe your reporting goal in natural language and the AI agent can create a complete data source configuration, including filters. This reduces the technical barrier for non-developer teams setting up new reports.
Supported Salesforce Data
Power BI Connector for Salesforce supports all standard and custom Salesforce objects available in your org, including objects from installed AppExchange packages. Objects from additional Salesforce products appear automatically without extra configuration.
Access is governed entirely by Salesforce permissions – if a field is hidden from a user in Salesforce, it does not appear in the connector for that user.
Native Connectors vs Power BI Connector for Salesforce: Side-by-Side
| Native Reports Connector | Native Objects Connector | Power BI Connector for Salesforce | |
| Row limit | 2,000 | None | None |
| Server-side filtering | No | No | Yes |
| Shared data sources | No | No | Yes |
| Incremental refresh | Not effective | Not effective | Yes |
| Salesforce-native | No | No | Yes |
| Audit trail | No | No | Yes |
| Setup complexity | Low | Medium | Medium (one-time) |
ETL tools like Fivetran or MuleSoft offer an alternative path that works well for organizations with existing data warehouse infrastructure.
Third-party connectors like CData provide another option; they operate as external middleware, meaning Salesforce data passes through CData’s infrastructure rather than traveling directly to Power BI.
For organizations with data residency requirements, strict security policies, or Salesforce governance standards, routing data through an external server is a meaningful concern. CData also requires a separate licensing agreement and operates outside the Salesforce AppExchange certification framework.
For teams that need Salesforce data in Power BI without ETL pipelines, external data routing, or additional vendor relationships, Power BI Connector for Salesforce keeps everything within your existing Salesforce environment with no third-party infrastructure involved.
Is Power BI Connector for Salesforce Right for Your Team?
Power BI Connector for Salesforce is designed for teams where the native path has created real operational problems: broken refreshes, inconsistent data across analysts, API quota failures, or lack of governance over what data is being exported and by whom.
It is particularly well-suited for enterprise Salesforce orgs with large datasets, teams using Salesforce across multiple departments, and organizations with data governance or compliance requirements.
For smaller teams with simple reporting needs and manageable data volumes, the native Objects connector may be sufficient.
Getting Started with Power BI Connector for Salesforce
Unlike ETL-based solutions that require pipeline configuration and infrastructure setup, the entire process happens inside tools you already use – Salesforce and Power BI. Most teams complete the setup in under two hours.
Step 1: Install from AppExchange
Find Power BI Connector for Salesforce on the Salesforce AppExchange and install it directly into your org. No external servers, no infrastructure provisioning, it installs like any other Salesforce app.
Step 2: Configure Salesforce (one-time)
A Salesforce administrator completes a one-time configuration: Connected App for authentication, and a Custom Setting to tie the configuration together. This is done entirely inside Salesforce Setup. Full instructions are in the Installation Guide.
Step 3: Create your first data source
Open Power BI Connector from the Salesforce App Launcher. Select the objects and fields your report needs, apply filters to scope the dataset, and save the data source. This is where the work happens – Power BI just reads the result.
Step 4: Connect Power BI
Generate an access token inside the Power BI Connector, copy the Power Query script from the data source list, and paste it into Power BI Desktop. Set the token as a parameter and load the data. Your Salesforce data is live in Power BI.
Not ready to install in production? The AppExchange listing includes a sandbox trial using your own org data, and a test drive option with a preconfigured environment that requires no setup at all.
Review the full documentation at metricasoftware.com/docs/salesforce/.
Conclusion
The best Salesforce Power BI connector depends on what your team actually needs. For production-grade reporting with no row limits, server-side filtering, centralized governance, and Salesforce-native architecture, Power BI Connector for Salesforce is the most complete option available without the overhead of a full ETL pipeline.
