[BUG]: DetailList : Can't add fields

[LSMetag]

In the DetailList settings, when I try to add new fields It doesn't do anything. I see fields of my Item source and can select it, but nothing happens when I click on Add, changes. The Items part is a formula that filters and sort a Collection.

To Reproduce
Steps to reproduce the behavior:

1. Go to DetailList Settings
2. Click on 'Fields'
3. Check a field to add
4. Nothing happens

Expected behavior
The field should add as the column template is ok, and the Collection field is correctly named and displayed in the list.

Screenshots

Additional context
On an already existing DetailList, I can remove fields, but not add them back.

I didn't see this behavior before June 2024, but as I read elsewhere It happened at May 2024. I made tests with May 2024 update and got the same behavior. Attempting an update on our existing app completely broke it, as It massively uses DetailLists.

AB#3642

[dinhmanh3a]

I'm also having the same problem recently. I use it a lot. We hope to be able to fix the error soon. Thanks a lot

[jean-goyat]

It's the same issue that was closed last week (see temporary workaround here)

Guess it shouldn't have been closed...

[KarolFilipKozlowski]

Also, I to report that bug.

[slgsperry]

I am having this issue as well.

[denise-msft]

Our team is currently investigating the issue reported. We will keep you updated on our progress.

[denise-msft]

We are having trouble reproducing the issue. Can we please have some help with more details to isolate the conditions to reproduce?

What Power Apps studio version is this occurring on?
Is this happening on any specific data sources?
Is this happening when you're adding certain formulas (e.g., Search/Filter/sort) vs binding directly?
Does this happen only when binding a direct reference to the data source (e.g., Accounts table directly) vs a collection?
Have you retried creating a fresh app from scratch to do a simple repro, or is this only happening in existing apps?

[LSMetag]

Sorry for the late reply. It seems fixed. Probably thanks to a Power Apps Studio update.

[denise-msft]

Thanks for letting us know and glad to hear it's fixed for you!