218 posts tagged with "Power Apps"

The App checker's Data source category shows a count, with the warning Unused data sources: This data source is not used in the app. Removing it will improve performance. It's telling the truth: no formula reads that data source yet. Whether to remove it depends on whether you're going to use it.

A yellow triangle appears next to a gallery, and the formula says Delegation warning. The "Filter" part of this formula might not work correctly on large data sets. The app still works today, but on a list with more than 500 items it will quietly miss some. The fix is to rewrite the part SharePoint can't run.

You select a gallery, insert a Text control, and it doesn't appear in the rows. It sits next to the gallery, outside it. With the gallery itself selected, Studio adds new controls beside it, not into its template. Select the template first.

You want a badge's color to follow its text, so you write Switch(Self.Content, ...) in its Intent. Studio underlines Content and says Name isn't valid. 'Content' isn't recognized. The modern Badge's text can't be read that way. Base the color on the same value the text comes from.

You set a label in a gallery to a SharePoint column, and instead of text you get a red error icon and Expected Text value. The column is a Choice column, and Power Apps gets a Choice as a record, not as text. Add .Value and it works.

The Career Development Plan app gets its first screen. When someone opens the app, the Home screen greets them by name and shows their job title and manager. Everyone sees a My plan button, and managers also see My team. Behind it are the app's named formulas, which every later screen reuses.

Max returns the largest of its numbers. Give it a list of values, or a table and a column, and it hands back the biggest. Beyond the obvious uses, like the latest score or the highest amount, it's handy for layouts: "make this as tall as whichever of these is tallest".

Not flips a true-or-false value: true becomes false, false becomes true. You'll use it constantly with checks like IsEmpty and IsBlank, which answer the opposite of the question you usually want to ask. Power Fx lets you write it as a function, Not(...), or as the ! operator.

Data has gaps: a first name nobody filled in, an optional field left empty. Coalesce gives you a fallback: it returns the first of its values that isn't blank. One short function replaces a longer If with IsBlank, and reads better too.

"Welcome, Olivia" is fixed text joined to a value from a formula. Power Apps gives you two ways to write that: the & operator, and string interpolation with $"...". They produce the same text; the difference is how readable your formula is. Here are both, tried side by side in Studio.