Named formulas in Power Apps using App.Formulas Microsoft Power Apps image 11

Do you use the App onstart to set a lot of variables? And then do you repeat this same within other places of the app to keep things up to date? The new named formulas in App.Formula might be a better option.

Named formulas in Power Apps using App.Formulas Microsoft Power Apps image 12

Enable Named Formulas

After last week’s post about the new PDF Function in Power Apps, I’m going to look at the new Named Formulas feature today.

To enable Named formulas you can go to the Settings in your app. Then switch on the Named formula feature. Notice that this feature is still experimental, but it is a great feature to try out ( in non production apps)

Named formulas in Power Apps using App.Formulas Microsoft Power Apps image 13

Configuring Named Formulas

Now you can configure within App.Formulas using lines of code like this:

X = CountRows(List)
named functions

It might look like there isn’t much of difference between the Set and the ‘=’ assignment. But there is!

Difference between the Set function and Named Formulas

With the Set function you will set a value to a variable. This means that every time you want the variable to be updated you will have to rerun the code.

With Named functions you don’t have to do this. As your data changes ( in my example the datasource List), the value given by the Named function will automatically change. So in the earlier example as the List is updated and refreshed, the value of X will automatically be updated too.

That is one thing less to worry about in your app.

Avatar for Pieter Veenstra

By Pieter Veenstra

Business Applications Microsoft MVP working as a Principal Architect at HybrIT Services Ltd. You can contact me using

4 thoughts on “Named formulas in Power Apps using App.Formulas”
  1. Thanks Peter I like how you’ve explained this, just to validate I have this right. Could I use this instead of a setting a selected item in a gallery via variable and do something like ItemId = gallery.selected.ID?

  2. That would certainly be the intention to reduce the code required in different locations around the app on various controls where possible. Would be much easier to maintain. Thanks Peter

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Discover more from SharePains by Microsoft MVP Pieter Veenstra

Subscribe now to keep reading and get access to the full archive.

Continue Reading