Studio erases my formulas

(1) Share

Report

Posted on by james_hathaway

427

So,

I have a Gallery, and in the Template of that Gallery I have about 10 Labels, with formulas that refer to pieces of data in each record (e.g. ThisItem.Name)...

... Nothing new here.

The problem is, If I go and amend the "Gallery.Items" formula (say, tweak the Sort Columns or the Filter)

- ALL MY LABEL FORMULAS ARE DELETED, and replaced with something generic that PowerApps thinks is correct (It seems to just assign record fields alphabetically).

"Oh, I can see you have a really complicated formula in that Label, to be helpful, I am going to remove it so that you have to create that formula again and again every time you change the Gallery Items formula"

I suspect that this is another example of Microsoft trying to be "helpful", and in actual fact, ruining all my work, and making everything take twice as long... (just like when trying to format bullet points in Word - Bl***y nightmare!)

This can't be the designed behaviour, can it?

Why on earth would PowerApps do something like this?

James.

Categories:

Building Power Apps

All responses (2)

Answers (1)

Sort by

iAm_ManCat 18,256 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Heya @james_hathaway

Yeah that sounds like a nightmare - are these the original labels that were included in the gallery or ones you have added?

This definitely sounds like a bug - is this still occurring, and can you provide steps to reproduce it?

Cheers,

Sancho
Verified answer

timl 37,287 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

@iAm_ManCat

For info, there are some more details about this bug in the following post.

https://powerusers.microsoft.com/t5/Building-Power-Apps/Why-do-some-canvas-app-galleries-get-completely-scrambled-when-I/m-p/1582931

It happened to me and the results were horrible to fix. At the time, the behaviour was quite easy to reproduce. Fortunately, I've not encountered this problem since, so maybe Microsoft have fixed this.

Perhaps if someone else experiences this problem and finds this post through a search, they post a message here so that we know the issue still exists.