Named Formulas in Canvas Apps: CONSTANTS AREN'T VARIABLES

[@Guano1983]

I'm using it also for dynamic content. For example for filtered data. Before I put everything in a collection, if I didn't want to repeat the filter statements over and over again. But than I had to make sure that I update the collection when ever I modify the data. Now with named formulas you can define everything in one place and it will be always up to date! Usable as a collection but so much easier to maintain ;). And it will only be calculated when needed, makes the start of the app faster.

[@iamintractable1805]

You do realize that the filter will not update when other user running the app make changes, or when a change is applied to the SharePoint/Data directly. In these cases, you have to refresh the Named Formula before using it. SO, I am not sure, as currently implemented, named Formulas are best for data. Also, you do not avoid delegation warnings which do not occur in collections. The author of the video is correct to point out that constants are perfect for Named Formulas. Also, note that the more complex you app the more disastrous it can be when changing a named formula..

[@Bicycleclip]

So great thank you 🎉

[@dustinshilala4802]

Do these offer performance improvements at all for Lookups on Dataverse or Sharepoint?

[@JenMayB]

Yes, i was wondering if they were a performance improvement over variables?

[@iamintractable1805]

Well variable can be changed in the app. The results of Named Formulas cannot.

[@bellcore1]

I'm purely a power platform developer. I'm aware of constants but still don't understand the benefit of using them over variables. Variables only change if you tell them to change so what's the difference/why use constants?

[@iamintractable1805]

On some platforms, constants are more efficiently stored and dont have the overhead of variables. Not sure that it true of Named Formulas.