Forum Discussion
Extremely Slow Connection to Salesforce since update
Hello cacevedo , Anonymous, rmiquel, Anonymous, Chathurangaab,
I'm not sure if folks have noticed this or not. But in the most recent update of Power BI desktop: Version: 2.33.4337.501 64-bit (March, 2016) querying the Salesforce Object appears to be working now.
It still takes a few minutes to process, but this has been working consistently for the last few days at different times of the day (both on and off peak hours) without fail (cross my fingers), so far.
I was able to download over 22,500 rows from an object, when before Power BI would crash around 15,000 or so.
Just thought I'd let everyone know in case they hadn't tried it recently.
Painful but effective resolution:
I rebuilt my entire data model and reports from scratch in a new document. Had the old one open to one side, then recreated the new one. For some reason, the new document has no problem with Salesforce at all. The old one still does. I'm sure there's something buried deep within the file but a few hours later, I'm happy and back in business.
PowerQuery Desktop...
I am totally struggling with a repeating problem.
This is a merged query to custom objects.
Top level query is to an Excel Table listing two (2) quote numbers.
The first merge is matching (left outer) to custom SFDC object "Oracle Quote" which returns two records.
Matching Quote number in first to Quote Number in second.
Still in the top level query, a second merge is to the "Quote Products", which according to my information should return some 80 matching records.
Matching quote Record ID in first (the id retrieved in the first merge query) with the Quote Id field in seconf (left outer).
Once in a blue moon this appears to run normally and completes in say a minute.
Most the time the query times out.
All the records are showing in the Editor.
It seems to be the refresh from Excel that is always a problem.
Extremely frustrating as we try to re-build our sales operations processes on top of Power Query (transitioning from lightwight, but likely to disappear one day ExcelConnector)
This error seems to have reappeared in the December 2017 Update. Can anyone else confirm if they are getting this error again?
