SQL Server environment variables (Entra) for Power Apps will save you time moving your solutions from one environment to another. For example, from an environment used for dev or test to a different environment used for test or production. Manually create environment variables in your solution or set a switch in your app to auto-create them for you when you add a data source to your app while in your solution. Note that this feature is specifically for Entra. Power Apps with shared connections (e.g., SQL Auth) continue with connection references.

There are two environment variables to set for SQL connections: server and database. The database environment variable depends on the server environment variable. First you create an environment variable for your server. Once that is created you can create an environment variable for the database that attaches to the server environment variable.

Use an environment variable by selecting to create data source and instead of creating a new server database combo, use the ‘Advanced’ tab to select the environment variable to bind to the controls in your app.

Use SQL Server environment variables (Entra) to easily enable professional deployment patterns. See the documentation for this feature for an in-depth discussion: Use environment variables in Power Platform solutions – Power Apps | Microsoft Learn

The post SQL Server environment variables available for Power Apps appeared first on Microsoft Power Platform Blog.

Like with SharePoint, this feature operates with any natively bound gallery where the gallery is directly populated by SharePoint and not by a collection or variable.

Using Copilot with filter

Open a running app that uses a gallery against SQL Server.  If you have a premium license (which is required for the SQL Server connector), then you will see an adorner on your gallery.

Copilot supports three kinds of queries – filter, sort, and search.  While you can type any query you might like, it suggests possible questions based on your data in your app at the time. Note that Copilot over SQL supports an additional verb “in” that SharePoint does not support. It will search for an occurrence of your search text inside of a record value.

Copilot then scopes the records to satisfy the query. It displays a “Filtered” badge in the upper right corner of the gallery.  The exact query that was executed is displayed as a tag. And you can continue to refine your query with additional details by adding more query commands.

Filter, sort, and search galleries with Copilot to filter provides five key benefits:

• Copilot makes end users more productive and saves time. If an author has not built in search and sort capabilities, Copilot enables this scenario and makes them more productive. End users save time with the ability to directly express their query in natural language.
• Copilot saves author’s development time. Authors save time developing apps because they don’t need to develop all the UI controls necessary for the app. Instead, they can rely on Copilot for this functionality.
• Copilot enables queries over the full query result – not just what you can see in the gallery. Users can filter, sort, and search on fields even if the application doesn’t provide UI controls for these tasks. For example, you can search for records even if the application doesn’t have a search bar.
• Copilot is query safe. It only generates queries that can be run on the server. Authors don’t need to worry about whether or not their queries can be delegated.
• Copilot keeps private data private. It only works with the data that is normally returned to the application. It doesn’t access fields that aren’t returned to the app in a gallery/grid or form.

Create a new app with Studio version on or after 3.24092.17 or re-publish an existing app with this version. Then access your app while it is running. (Copilot with filter only appears at runtime, it does not appear inside of Studio.) Select an item in the gallery to start using Copilot with filter.

See the documentation for this feature for more details. https://learn.microsoft.com/en-us/power-apps/user/smartgrid

The post Use Copilot to quickly filter, sort, and search canvas app galleries with SQL Server appeared first on Microsoft Power Platform Blog.

Using Copilot with filter

Open a running app that uses a gallery against SharePoint.  If you have a premium license, then you will see an adorner on your gallery.

Copilot supports three kinds of queries – filter, sort, and search.  While you can type any query you might like, it suggests possible questions based on your data in your app at the time.

Copilot then scopes the records to satisfy the query. It displays a “Filtered” badge in the upper right corner of the gallery.  The exact query that was executed is displayed as a tag. And you can continue to refine your query with additional details by adding more query commands.

Filter, sort, and search galleries with Copilot to filter provides five key benefits:

• Copilot makes end users more productive and saves time. If an author has not built in search and sort capabilities, Copilot enables this scenario and makes them more productive. End users save time with the ability to directly express their query in natural language.
• Copilot saves author’s development time. Authors save time developing apps because they don’t need to develop all the UI controls necessary for the app. Instead, they can rely on Copilot for this functionality.
• Copilot enables queries over the full query result – not just what you can see in the gallery. Users can filter, sort, and search on fields even if the application doesn’t provide UI controls for these tasks. For example, you can search for records even if the application doesn’t have a search bar.
• Copilot is query safe. It only generates queries that can be run on the server. Authors don’t need to worry about whether or not their queries can be delegated.
• Copilot keeps private data private. It only works with the data that is normally returned to the application. It doesn’t access fields that aren’t returned to the app in a gallery/grid or form.

Getting started

Choose a build after 7.4 (expected on 7/29) and make sure you’ve also re-published your app on 7.4 or later. Then access your app while it is running. (Copilot with filter only appears at runtime, it does not appear inside of studio.) Select an item in the gallery to start using Copilot with filter.

See the documentation for this feature for more details. https://learn.microsoft.com/en-us/power-apps/user/smartgrid

The post Use Copilot to quickly filter, sort, and search canvas app galleries with SharePoint lists appeared first on Microsoft Power Platform Blog.

Getting started

To use this feature, you need to either create a new SQL connection to your app or already have one in your app. In the table selector, choose the ‘Stored Procedure’ tab and select all of the stored procedures you want to access in your app. Then you can directly access the stored procedure in your app by referring to the data source name and then ‘dot’ into the specific stored procedure in a Power Fx formula.

This feature is an extension to the tabular model. We allow the ability to execute stored procedures, but we do not allow the ability to run arbitrary SQL. This helps provides an additional level of security. Additionally, you can bind a stored procedure directly to a gallery or table by checking the ‘Safe to use for galleries and tables’ checkbox.   

See the article Connect to SQL Server from Power Apps for a discussion of how and when to select this option and other details on how to use this feature.

The post Call SQL Server procedures directly in Power Fx (GA) appeared first on Microsoft Power Platform Blog.

Now anyone can comment a formula to provide help to those who inspect it later.

Commenting Styles

We make two commenting styles possible: line and block.

Line Comments

A line comment is one that comes at the end of a formula and takes up the rest of the line. For instance, if your formula looks like the following:

You can add line comments by adding a “// <your comment here>” at the end of the line like so:

You can’t put any code at the end of the comment – the comment runs all the way to the end of the line. And, the formula assumes that the next line picks up where the comment on the previous line began.

Block Comments

The other style of comment is block comment. As shown below, it starts with the special key combination of forward slash and an asterisk and continues until explicitly terminated with the opposite key combination of asterisk forward slash.

Note that you can use the block style comment at the end of a line as well. But the line style comment is easier to use for an end of line comment.

And, sometimes people use the end of line comment in the same way the block style comments are used.

But, it’s up to you. Pick a style that works for your formulas in your PowerApp. We’d love to hear from you about this feature in the PowerApps Community.

Thanks,

The PowerApps team.

The post Comment your PowerApps code! appeared first on Microsoft Power Platform Blog.