Passing Parameters to Power BI through Stored Procedure

[v-kumdee]

There Should be Provision of passing the Parameter to the report like we do in SSRS Reports. There should be any method to execute Stored Procedure by passing the Parameters

[nishalit]

Execute stored procedure parameters

[Lee_Aheron]

Calling stored procedures, with and without parameters, is definitely needed as much of the heavy lifting can be done using SQL Server or other databases to take advantage of what they do best. This ability also needs to include the ability to call AWS RedShift stored procedures, with and without parameters. Currently RedShift requires two (2) SQL statements, one to execute the procedure and one to get the results. Power BI Desktop and Report Builder need to handle those two (2) statements. Even if the statements need to be separated by a semicolon or other character.

[dgorman]

I echo the better stated comments already posted. The underlying data behind a slicer selection should be able to be passed as a parameter to a SQL SPROC call.

[Roan_D_Whitefoo]

It's absolutely ridiculous this feature isn't included yet. I work in an enterprise environment that has used parameterized stored procedures in SSRS reports for more than a decade. Recently we were asked to convert SSRS reports over to Power BI, which should have been a simple process. However, the lack of SP and parameter support has left us trying to "hack" a solution so our (very, very basic) reports can be converted.

I'm going to be suggesting we use something else instead of Power BI, or that we just go back to SSRS. And this is obviously a feature that has been requested since Power BI was launched. Why in the world would such an obvious and expected feature not be included??? I would never have imagined MS would release a reporting tool that is missing the most basic functionality.

For now, Power BI is useless for us unless we want to go back and completely rewrite every single one of our reports to no longer use Stored Procedures and parameters, which is just not going to happen.

[Frank_Kress1]

I can already find posts from 2017 on the web. All questions about this feature. Namely for "POWER BI Desktop".

All this is already possible in the paginated report (Report Builder).

And the report builder is ancient.

It's already the year 2023 and there hasn't even been a statement from Microsoft yet.

Maybe we should switch to Tableau Desktop after all?

Because the license we pay you for the reporting service is not small.

What I find annoying is that I now have no solution as to how we can migrate to the cloud.

At the moment it's time to keep looking and hope that I'll find a solution soon. Hardcore would be if I develop the shi... with Access report generator.

[andrey_kudryave]

We use Power BI in combination with SQL Server. For many of our tables, we maintain system versioning, which allows us to "travel back in time." The point in time to travel is selected by the user, leaving us with a few options:

1. Import History Tables into Power BI:
2. This approach places significant pressure on infrastructure due to the large size of the tables and results in a poor user experience. Additionally, we lose near real-time data freshness and nice sql syntax "FOR SYSTEM_TIME AS OF ".
3. Use M Parameters with SQL Query Manipulation:
4. This setup involves manipulating SQL queries as strings. While it can be done, it is super obscure way that makes sense only for very simple "SLECT * FROM " type of queries. Something a little more complex will be very difficult to write, read, change, and test.
   Fallback to SSRS Reports:
   Currently, this is our chosen solution.

   The same logic applies to any situation where a large amount of data for fetching could be significantly reduced by applying user selection.

   We aim to phase out SSRS and fully adopt Power BI. However, Power BI still lacks features to effectively supersede SSRS in scenarios like these. Is there a plan to address this limitation and improve the situation?