Forum Discussion
rharrison2641
2 years agoNew Member
How to resolve OLE DB or ODBC timeout error when pulling in a large object from Salesforce
Hello, I will preface this by saying that I am new to PowerBI, but experienced in Salesforce. I am trying to pull in several objects into a PowerBI report by going to Get Data>Salesforce Objects>...
metrica
Post Prodigy
3 months agoHi rharrison2641,
The OLE DB/ODBC timeout on Salesforce Objects is almost always a volume issue, not a configuration one - Power Query tries to pull the entire object (hundreds of thousands of rows + all columns by default) before any filtering applies, and the default command timeout (10 minutes) isn't long enough.
Two native paths worth trying first:
- Increase command timeout in the M code (Power Query Editor → Advanced Editor): add [CommandTimeout=#duration(0, 0, 30, 0)] to your Salesforce.Data(...) call to bump it to 30 minutes. Doesn't help with the underlying volume, but buys you time.
- Use the Select Query advanced option when connecting - supply a custom SOQL with only the fields you need (SELECT Id, Name, CreatedDate, ... FROM YourObject WHERE LastModifiedDate >= LAST_N_DAYS:90). Shorter query, much smaller payload, no timeout.
If hand-writing SOQL isn't ideal, Power BI Connector for Salesforce on AppExchange handles this through a UI inside Salesforce:
Why it might fit:
- Filter conditions and field selection configured on the Salesforce side - only the rows you need are pulled, no timeout
- No 2,000-row limit on reports
- Supports custom fields, custom objects, and joined reports
- 30-day free trial
- Setup docs: https://metricasoftware.com/docs/salesforce/
- Responsive support if you get stuck: https://metricasoftware.com/docs/salesforce/contact-support/
Happy to set up a quick demo on your specific object. Just reach out via the support link.
Cheers,
Metrica Team.