Answered

Combo boxes do not maintain settings, especially SearchFields and DisplayFields

(0) Share

Report

Posted on by Len C

379

I am trying to set various the SearchFields and DisplayFields properties on numerous Combo boxes. The changes keep getting erased. They work for maybe one test run within maker portal, then revert to whatever default single field PowerApps thinks is the best one.

I've tried saving the app immediately after changing the properties, then verifying they still show. Inevitably, the values disappear.

I've tried configuring the fields using the 'Fields' pop-up; typing them directly into the property pane; and typing them directly into the formula bar.

Is this a known issue? Any work-arounds or ETA on when this will be fixed??

Categories:

Building Power Apps

I have the same question (0)

All responses (9)

Answers (1)

Sort by

RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@LenC

Please open a support ticket for your issue. This is a common thread for the past several days and it appears that the latest release has some bug introduced.

The more open tickets on this issue, the more attention it will get from the product team.

I hope this is helpful for you.

Was this reply helpful? Yes No
zYx 78 on at

Like
a
(0)

Report
Copy link

Link copied!

@LenC, in our case, those two fields are defaulted to the first column name in alphabetical order hence why we temporarily renamed all columns we use in combo boxes to begin with AA, i.e. AAStaffName etc., we use collections.
We had to change the code in many other places to reflect these changes, but we have our app connected to GitHub, and it can be quickly done by the "find and replace" in all files in Notepad++.

Was this reply helpful? Yes No
Len C 379 on at

Like
a
(0)

Report
Copy link

Link copied!

What if you are trying to set those fields to a Table of column names? The '2-field' option for Display, for example, or a list of columns for Search.

For example, in a field where the user is supposed to select a cost code, I was showing the Cost Code number, and on the second line, the Description.

And, seriously, you are renaming your Dataverse columns to work around this? I thought you can't rename the original column name, only the column's Display Name. But the Combobox fields use the immutable internal column name, don't they?

Was this reply helpful? Yes No
Len C 379 on at

Like
a
(0)

Report
Copy link

Link copied!

@RandyHayes, where do you open a ticket? Does it have to be in the M365 Admin portal?

Was this reply helpful? Yes No
zYx 78 on at

Like
a
(1)

Report
Copy link

Link copied!

All affected “double” combo boxes are not working. The second option blanks out when the app is loaded in studio.

We use SharePoint and we collect the data into collections in App.OnStart and we rename those columns in the collection and not in SP.

Was this reply helpful? Yes No
zYx 78 on at

Like
a
(1)

Report
Copy link

Link copied!

You can normally open a ticket via the Power Apps Admin portal, but their bot was not working properly so I opened a ticket through the M365 admin portal. Just don't use “PowerApps” in the subject as they will try to redirect you to the Power Apps admin portal.

Was this reply helpful? Yes No
Len C 379 on at

Like
a
(0)

Report
Copy link

Link copied!

Oh, nice!

Was this reply helpful? Yes No
Len C 379 on at

Like
a
(0)

Report
Copy link

Link copied!

For those willing to open a Support Case to help get this resolved faster, here are some links to the recent threads I found reporting this issue:

Combobox DisplayFields and SearchFields resettomg - Power Platform Community (microsoft.com)

Re: Combo boxes do not maintain settings, especial... - Power Platform Community (microsoft.com)

Power Platform/Apps - Canvas App- Combo BOX issue ... - Power Platform Community (microsoft.com)

Re: Massive bug in ComboBox causing chaos! The Dis... - Page 2 - Power Platform Community (microsoft.com)

Was this reply helpful? Yes No
Verified answer

Len C 379 on at

Like
a
(0)

Report
Copy link

Link copied!

FYI, Microsoft Support acknowledged the bug, and created this work-around: Go into App Settings, and change the Authoring Version of PowerApps:
I'm actually not sure which version is the good one. MS had me set it to the last one in the list, rather than the 'recommended' one, but today I"m back on a 'recommended' one. Perhaps this auto-updates with new releases, and I managed to skip the bad one. They did not provide any guidance on how the authoring version is set.

If you are having the issue, try changing to an older one.

Was this reply helpful? Yes No