Power Apps release 3.21023.26 completely broke my app

[EdwardAhn]

Anyone else having issues with the new release? Yesterday my app was working perfectly under version 3.21022.27.

Today, with the new release 3.21023.26 my app is unusable.

From what I can tell, there is something broken about the handling of potentially blank records/values, and my conditionally visible/positioned objects are all over the place, and my navigation on conditional screens are also not working at all.

[laurent68000]

Thank you Edward. At least we can keep working... But i hope they will a fix. I don't want to be stuck with version 3.21022.27.177523192

[Faatimah]

Same for me. On Play, app works fine, even after I make any changes. Just when on Edit, nothing works. Images doesn't display, OnSelect doesn't work. Sizes are not as it should be.

[sridutt]

Thanks everyone for reporting issue, we shipped fix for issue this issue with 3.21023.28 version. Please let us know if you are still seeing any issues in latest release.

[vblease]

YES!

I posted similar here:

https://powerusers.microsoft.com/t5/Building-Power-Apps/Multiple-issues-in-PowerApps/m-p/843631#M268...

What a nightmare! 

[vblease]

Hi Sridutt,

I'm having an issue with multi select combo boxes, it was first reported to me by a colleague on Friday 26th Feb.

I can see in one specific app's versions, the following releases were applied, and the problem continues after the release of 3.21023.28:

3.21023.26  25/02
3.21022.27  26/02
3.21023.28 28/02

To try and explain,

When I load a screen I set the DefaultSelectedItems of a combobox to values stored in the database. The control displays correctly and I can see the highlighted tags of the selected items.

The following is pseudocode for my setting the DefaultSelectedItems property:

Filter(
'[dbo].[TABLENAME]',
FIELD1 = VARIABLE.ID
).FIELD2

If the user clicks a save button on the screen, I write the DefaultSelectedItems back to the database regardless of if the user has manually changed these values.

The following is pseudocode for me inserting these values back to a database table:

Remove(
'[dbo].[TABLENAME]',
Filter(
'[dbo].[TABLENAME]',
FIELD1 = VARIABLE.ID
)
);

Collect(
'[dbo].[TABLENAME]',
ForAll(
COMBOBOX.SelectedItems,
{
FIELD1: VARIABLE.ID,
FIELD2: COMBOXVALUEFIELD2
}
)
);

Up to last week this was working as expected.

I now see behaviour whereby the combobox intermittently loses the values saved in DefaultselectedItems when clicking save; the result is no data is written to the database and the next time the screen loads the same combobox is empty (because there is no data to retrieve from the database).

Prior to these updates I'd saved a version of an affected app on 12th Feb (3.21021.39) and everything was working fine. I'm testing now after the release of 3.21023.28 and the problem continues.

I would appreciate advice how to resolve this please? I have built 2 apps in Power Apps and they are both exhibiting this behaviour.

[LaelH]

There are all sorts of symptoms to this issue - it seems to be quite broad based. See also

 Solved: Re: PowerApps not functioning - Power Platform Community (microsoft.com)

[CarlosFigueira]

Hi @vblease ,

Your expression to remove/add items from the table has a "race condition" - two things that can happen in an arbitrary order that may affect the outcome of the expression. After the Remove function completes, two things can happen (and Power Apps does not guarantee in which order they will happen😞 since the table '[dbo].[TABLENAME]' was changed, the expression for the DefaultSelectedItems in the combo box is re-evaluated (and since the previous selections were removed, an empty table will be returned); or the Collect function can be evaluated, adding the selected items from the combo box to the table. It seems like the former is going on, so to ensure a consistent outcome, the app should save the current selections prior to deleting the items from the table, something like the expression below:

Collect(currentSelection, COMBOBOX.SelectedItems);
Remove(
    '[dbo].[TABLENAME]',
    Filter('[dbo].[TABLENAME]', FIELD1 = VARIABLE.ID)
);
Collect(
    '[dbo].[TABLENAME]',
    ForAll(
        currentSelection,
        {
            FIELD1: VARIABLE.ID,
            FIELD2: COMBOXVALUEFIELD2
        }
    )
)

Hope this helps!

[vblease]

This was bang on advice. Thank you so much!

[gazzo1967]

This is now fixed?? i believe after speaking directly to a developer!