Skip to main content

Power BI

New

Allow passing of paramaters to Salesforce Reports connections

Vote (56) Share
Dory Owen's profile image

Dory Owen on 15 Apr 2016 09:22:58

Parameters can be added to Salesforce report URL as explained here:
http://pragmaticforce.blogspot.com/2011/08/passing-report-criteria-via-dynamic_9002.html

Search for "reportFilters" in the API doc here: https://resources.docs.salesforce.com/sfdc/pdf/salesforce_analytics_rest_api.pdf

This would allow us to limit individual queries to

Comments (3)
Dory Owen's profile image Profile Picture

b43337fc 59bf-4ee9-b744-4542ac791479 on 05 Jul 2020 22:38:10

RE: Allow passing of paramaters to Salesforce Reports connections

Yes please, pretty isn't important, but please expose more options.

Dory Owen's profile image Profile Picture

d5ea54fe 02cc-4912-9dbf-4086e6294678 on 05 Jul 2020 22:29:57

RE: Allow passing of paramaters to Salesforce Reports connections

There are a number of limits set by Salesforce on API calls for Salesforce Reports. It is reasonable to think Excel report can support more than 2,000 rows on a typical report. That is first roadblock to resolve. In addition to that, there are other limits such as user concurrency and number of API calls per hour.
Ideally, Microsoft is able to discuss with Salesforce to understand how best to use this connection without reaching any limits and allowing Power Query and Power BI be utilized using Salesforce Reports data.

Dory Owen's profile image Profile Picture

d748525c af8a-47fa-aad2-5d92d6d23e76 on 05 Jul 2020 22:19:33

RE: Allow passing of paramaters to Salesforce Reports connections

Misspelled parameters. (This UI on Edge is wrapping text at every third word. Disorienting...just me? Weird.) I've been able to build a standard report in SF and then add params to the URL to narrow results. But cannot get these params added via Power Query. It looks like the API can pass params. The trick is to provide some way for us to add them to Power Query M statement. Without this workaround the limit of 2000 rows makes this feature almost useless because one never knows if results are complete.

Potentially, I could pull first 2000 rows sorted by ID, then pass ">LastID" and get the next 2000 rows. Or, just limit standard report to only one Account or Owner or Rep to ensure results are limited to small # of rows.