Salesforce data load stops at 128001

[fcivardi]

I try lo load the Account table  and it stops at 128.001 with one error (I've seen there is another post with the same problem). If I refer to the same query, I can get different numbers:

-- 128.001 rows

#Account table

let
    Source = Salesforce.Data(),
    OpportunityLineItem = Source{[Name="Account"]}[Data],
    #"Removed Other Columns" = Table.SelectColumns(OpportunityLineItem,{"Id", "Name", "RecordTypeId"})
in
    #"Removed Other Columns"

-- this refers to the previous query and gets 222.001 rows:

let
    Source = #"Account Table"
in
    Source

[ReportMaster]

Hi @fcivardi were you able to find a solution? As a workaround, maybe you can try to test your connection with a 3rd party connector, which pulls data from the SF objects API which has less strict limitations. I've tried windsor.ai, supermetrics and funnel.io. I stayed with windsor because it is much cheaper so just to let you know other options. In case you wonder, to make the connection first search for the Salesforce connector in the data sources list:

After that, just grant access to your Salesforce account using your credentials, then on preview and destination page you will see a preview of your Salesforce fields:

There just select the fields you need. It is also compatible with custom fields and custom objects, so you'll be able to export them through windsor.  Finally, just select PBI as your data destination and finally just copy and paste the url on PBI --> Get Data --> Web --> Paste the url. 

[BIUser1524]

Has anyone identified the solution to this problem? I am getting the same error "URL too long". I tried Power BI as well as Excel PowerQuery and I get the same error. It think it is because the table has too many columns. The error message gives the URL and it is all (or most) of the columns listed one after another. I don't have any ability to update the table or change the number of columns. Any help would be hugly appreciated!

[Beckham]

This happens ALL THE TIME at our organization. It's not pulling in all the rows from Salesforce. 

The only work around we've been able to figure out, is to load the entire object into excel without filtering anything in powerquery (from what I understand, when you filter in powerquery, it bumps into salesforce's restrictions very fast). Then once it's loaded into a table, create a new query and link to the loaded table. Then perform your transformations in a second query locally.

[joeort]

I have the same problem.  PBI Support keeps telling me to update to the latest version (which I have - currently Jan 2016) and that's supposed to fix it.  It's made the product unreliable and frustrating to work with.

I've had lower numbers pull through and still get the error which then cascades into the later tables not loading at all (1 row loaded 1 error; turns out it's a blank table row).  Contact tables have loaded at 234 and 1 error and 82,001 and 1 error.

[Greg_Deckler]

Generally when I have run into similar issues it comes down to some bad data. I had similar issues with certain fields in Microsoft CRM when loading Leads. That being said, it looks like you are only loading a single field so you can't get around it like I did by removing fields. What is the error?

[fcivardi]

How can I see the error?  I only see " loaded x rows with 1 error"

[pqian]

@fcivardi Can you run the following query:

= Table.SelectRowsWithErrors(PreviousStep)

[fcivardi]

DataSource.Error: The operation has timed out Details: https://my.salesforce.com/services/data/v29.0/query/01g2000002x2iwbAAA-128000

[qa4432]

Not sure how you are connecting into Salesforce.com but be aware that Salesforce.com has execution Governors and Limits to prevent performance issues.  It is quite possible that Salesforce.com connectivity is telling you that you are limited in the data you can extract.

Check out the url below for more info.....

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm

Diana

[Greg_Deckler]

@fcivardi - Probably the best thing to do would be to turn on logging. Go to File | Options & Settings | Options | Diagnostics and check the box to enable Tracing. Run the data load and then take a look at the trace file.