SQL - How to return data from Stored Procedures to Power Apps

If you're looking to call SQL Server Stored Procedures from Power Apps, this post walks through this new feature and demonstrates how to display and use the return values from an app.

During the past week, one of the most exciting developments is the addition of direct SQL Stored Procedure support to Power Apps.

This post takes a closer look at this new feature, including the benefits and an explanation of how to call a Stored Procedure from Power Apps. 

What's the benefit of using Stored Procedures?

Stored Procedures can help build much more performant apps. For instance, we can use them to overcome delegation limitations that prevent us from retrieving data from large tables. Stored procedures can also improve performance by providing a means to add and update multiple rows of data through a single call. 

They also enable us to build more resilient apps by providing support for transactions. This is particularly valuable when updating data from multiple tables.

How to get started with calling Stored Procedures from Power Apps

To use Stored Procedures from Power Apps, the first step is to enable the "SQL Server Stored procedure" option in the Upcoming features section of the app Settings. Once enabled, we can access Stored Procedures directly from PowerFx formulas in Power Apps.

How to retrieve records from a Stored Procedure

To demonstrate how to retrieve records from a stored procedure, let's take the example of the following procedure that selects records from a table based on an input parameter. The definition of the stored procedure looks like this.  

CREATE PROCEDURE [dbo].[GetProduct]
@ProductID uniqueidentifier
WHERE [ProductID] = @ProductID;

To call this Stored Procedure from Power Apps, we add a connection to SQL server in the same way as as we would add a SQL table or view. In the right-hand panel, a 'Stored procedure' tab now appears. From here, we can select our stored procedure.
To display the return value of a stored procedure in a gallery, table, or some other data control, we need to click the 'Safe to use for galleries and tables?' checkbox.

If we leave this checkbox unchecked, the call to Stored Procedure will be behavioural, meaning that if we want to retrieve the results, we would do so by calling the Stored Procedure from a button and storing the result in a variable or collection.

With the 'Safe to use for galleries and tables?' checkbox checked, we can directly set the Items property of a data table control to the Stored Procedure call, as shown beneath.

Note that calls to Stored Procedures return a record called ResultSets. This contains one or more Table objects that correspond to the result sets that are returned by the procedure. Because our Stored procedure returns a single result set, the results of the procedure are contained in a table called Table1.

Working with multiple result sets from Stored Procedures

To demonstrate a Stored procedure that returns multiple result sets, let's take the example shown below. This Stored procedure returns two result sets - a row from a Property table that matches the ID of an input parameter, and a row from a 'Property Image' table that matches the ID parameter.

CREATE PROCEDURE [dbo].[GetPropertyDetails]
@PropertyID int

propertyid, Address1, Address2, City
WHERE PropertyID=@PropertyID

WHERE PropertyID=@PropertyID
 The image below highlights the output when we call this Stored procedure from Management Studio.

From Power Apps, we can call this Stored procedure by adding a button and applying the following formula to the OnSelect property.

When we click the button, it sets the return value to a variable called varPropertyDetail.

As we see here, the ResultSets record within varPropertyDetail contains 2 tables - Table1 and Table2.

Table 1 contains the first result set.

Table 2 contains the second result set.

Are there any data retrieval limitations?

When we collect data directly from a SQL table or view, the Collect and ClearCollect functions return a maximum of 2000 records or the maximum number that's defined in the 'data row limit' setting of an app.

The great thing about calling a Stored procedure is that this limit does not apply.

Let's take this example Stored procedure that returns a sequence of numbers. The number of records returned depends on an input parameter.

CREATE PROCEDURE [dbo].[GetNumberSequence]
@RowCount INT
SELECT 1 AS Number
SELECT Number + 1
WHERE Number < @RowCount
SELECT Number,
'Row number ' + CAST([Number] AS VARCHAR) AS [NumberDesc]
If we execute this procedure from Management Studio with an input value of 8,000, this is the output that's returned.

From Power Apps, we can populate a collection with the return value of this Stored Procedure by calling ClearCollec like so:


As we see from the screenshot below, the resulting collection contains the full 8,000 rows.

This is great news for Power App builders who may have struggled in the past with populating large connections.


The ability to call Stored Procedures directly from Power Apps is now available. This is a great enhancement because it enables us to build better-performing apps, and to take advantage of other benefits of Stored Procedures, including modularity of logic, better reusability and maintainability. This post walked through some examples of how to call Stored Procedures and consume their results from inside Power Apps.
  •   Categories: 
  • sql