cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
SynergyM
Level: Powered On

Re: A bug has occurred since the last version of powerapps (3.19052.19)

@_Corey_  The date value is being referenced in a gallery.  6 galleries actually, but only 2 of them are visible when the app loads. 

 

Each of those two visible galleries have an Items property set like this code block.  The values "selectMonday", "selectTuesday", etc are the date values that changed and then the published app started disappearing.  The app starts with focusMode = false.

If(Not(focusMode),
  Table(
     {DAY: "U_MON", delDate: selectMonday}
    ,{DAY: "U_TUE", delDate: selectTuesday}
    ,{DAY: "U_WED", delDate: selectWednesday}
    ,{DAY: "U_THU", delDate: selectThursday}
    ,{DAY: "U_FRI", delDate: selectFriday}
    ,{DAY: "U_WEE", delDate: selectSaturday}
  )
  ,Switch(Text(DatePicker1.SelectedDate, "[$-en-US]dddd")
        , "Monday",   Table(
                                {DAY: "U_MON", delDate: selectMonday}
                                ,{DAY: "U_TUE", delDate: selectTuesday}
                                ,{DAY: "U_WED", delDate: selectWednesday}
                            )
       , "Tuesday",   Table(
                                {DAY: "U_MON", delDate: selectMonday}
                                ,{DAY: "U_TUE", delDate: selectTuesday}
                                ,{DAY: "U_WED", delDate: selectWednesday}
                            )
       , "Wednesday", Table(
                                {DAY: "U_TUE", delDate: selectTuesday}
                                ,{DAY: "U_WED", delDate: selectWednesday}
                                ,{DAY: "U_THU", delDate: selectThursday}
                            )
       , "Thursday",  Table(
                                {DAY: "U_WED", delDate: selectWednesday}
                                ,{DAY: "U_THU", delDate: selectThursday}
                                ,{DAY: "U_FRI", delDate: selectFriday}
                            )
       , Table(
                {DAY: "U_THU", delDate: selectThursday}
                ,{DAY: "U_FRI", delDate: selectFriday}
                ,{DAY: "U_WEE", delDate: selectSaturday}
              )
  )
)

I have a boolean variable called loadingNow that I set to true when the app is first loading data.  For the two visible galleries, if I wrap the Items property like this, the app loads successfully and never disappears.  For now I'm leaving it like this to keep it working.

If(Not(loadingNow),
If(Not(focusMode),
  Table(
     {DAY: "U_MON", delDate: selectMonday}
    ,{DAY: "U_TUE", delDate: selectTuesday}
    ,{DAY: "U_WED", delDate: selectWednesday}
    ,{DAY: "U_THU", delDate: selectThursday}
    ,{DAY: "U_FRI", delDate: selectFriday}
    ,{DAY: "U_WEE", delDate: selectSaturday}
  )
  ,Switch(Text(DatePicker1.SelectedDate, "[$-en-US]dddd")
        , "Monday",   Table(
                                {DAY: "U_MON", delDate: selectMonday}
                                ,{DAY: "U_TUE", delDate: selectTuesday}
                                ,{DAY: "U_WED", delDate: selectWednesday}
                            )
       , "Tuesday",   Table(
                                {DAY: "U_MON", delDate: selectMonday}
                                ,{DAY: "U_TUE", delDate: selectTuesday}
                                ,{DAY: "U_WED", delDate: selectWednesday}
                            )
       , "Wednesday", Table(
                                {DAY: "U_TUE", delDate: selectTuesday}
                                ,{DAY: "U_WED", delDate: selectWednesday}
                                ,{DAY: "U_THU", delDate: selectThursday}
                            )
       , "Thursday",  Table(
                                {DAY: "U_WED", delDate: selectWednesday}
                                ,{DAY: "U_THU", delDate: selectThursday}
                                ,{DAY: "U_FRI", delDate: selectFriday}
                            )
       , Table(
                {DAY: "U_THU", delDate: selectThursday}
                ,{DAY: "U_FRI", delDate: selectFriday}
                ,{DAY: "U_WEE", delDate: selectSaturday}
              )
  )
)
)

The "select" dates used to be pulled from a Flow using a SQL Server Stored Procedure.  Now they come from a chunk of code that executes from the page's OnVisible property:

Concurrent(
    Set(selectMonday, DatePicker1.SelectedDate - Weekday(DatePicker1.SelectedDate, MondayZero)),
    Set(selectTuesday, DatePicker1.SelectedDate - Weekday(DatePicker1.SelectedDate, MondayZero) + 1),
    Set(selectWednesday, DatePicker1.SelectedDate - Weekday(DatePicker1.SelectedDate, MondayZero) + 2),
    Set(selectThursday, DatePicker1.SelectedDate - Weekday(DatePicker1.SelectedDate, MondayZero) + 3),
    Set(selectFriday, DatePicker1.SelectedDate - Weekday(DatePicker1.SelectedDate, MondayZero) + 4),
    Set(selectSaturday, DatePicker1.SelectedDate - Weekday(DatePicker1.SelectedDate, MondayZero) + 5),
    Set(selectSunday, DatePicker1.SelectedDate - Weekday(DatePicker1.SelectedDate, MondayZero) + 6)
)

 

Something else I noticed when the app finally loaded correctly today is that many of the gallery height/width/x/y values that I had referencing other galleries within groups were not working at all, causing several graphical problems.  For now I hard set the values that stopped working.

 

For the carriage return bug I tried your workaround, but no luck yet. Here's what I've tried:

Substitute(
    ThisItem.Day & "
" & Text(DateValue(Text(ThisItem.Date)), "[$-en-US]m/dd")
, Char(13), Char(10))

Output:  "Mon 6/24"

 

And

Substitute(
    ThisItem.Day & "
" & Text(DateValue(Text(ThisItem.Date)), "[$-en-US]m/dd")
, Char(10), Char(13))

Output:  "Mon6/24"

 

And

ThisItem.Day & Char(10) & Text(DateValue(Text(ThisItem.Date)), "[$-en-US]m/dd")

Output:  "Mon 6/24"

 

And

ThisItem.Day & Char(13) & Text(DateValue(Text(ThisItem.Date)), "[$-en-US]m/dd")

Output:  "Mon6/24"

 

Thanks for all your help.

Ginevra
Level: Powered On

Re: A bug has occurred since the last version of powerapps (3.19052.19)

HELP @_Corey_  , and rest of Microsoft team! A similar bug has appeared again in one of the last versions you released :(. Everything worked fine until we published a new version yesterday with minor design updates, and now the following happens:

( Intro: in my StartScreen I choose one of 3 locations, and this choice navigates me to a screen with a gallery, filtered on the chosen location)

- The first time I open a gallery, the first item is not fully shown: some of the labels are empty

- If I go back to previous screen, and enter again, the first item is now from another location!!

- If I click on an item of the gallery to go into EditScreen> EditForm for that item, all fields are empty the first time. Only the item number on top of the page is right. But if I go out and in again, the content of the fields appears. This is ESPECIALLY dangerous because users will think that they need to fill in the fields-when they actually already have content in the datasource!

 

Attached you can find screenshots of the problem.

 

App version 3.19074.24.

Over 100 people in the field using this app, so I hope a solution is found soon!!

 

Thanks in advance,

Ginevra

PowerApps Staff _Corey_
PowerApps Staff

Re: A bug has occurred since the last version of powerapps (3.19052.19)

@Ginevra Can you please provide a session ID for an affected session? 

Can I also ask what your underlting data source is? SQL? SharePoint? CDS?  

Finally, can you verify if the Use longer data cache timeout and background refresh setting is enabled in App settings -> Advanced settings.  If so, can you please disable it?

In the meantime, I would suggest restoring the last known good version of your app, if possible.

 

 

Ginevra
Level: Powered On

Re: A bug has occurred since the last version of powerapps (3.19052.19)

Hi @_Corey_ , thanks for the quick reply.

 

The underlying data source is SharePoint.

 

The advanced setting you mention was On and I turned it off. I then saved and published (I can do the tests on a copy of the app, a test-app), but the bugs persist. 

Here is a session ID AFTER I have switched off the setting mentioned: 

A session ID: 44a42a7e-c216-489b-9ceb-51ab4868b29c
PowerApps 3.19073.18

 

I did the restore as you suggested, thanks for the tip!

LukeC
Level: Powered On

Re: A bug has occurred since the last version of powerapps (3.19052.19)

Sounds like the previous patch needs to be rolled back. Problems everywhere

PowerApps Staff _Corey_
PowerApps Staff

Re: A bug has occurred since the last version of powerapps (3.19052.19)

@Ginevra  Studio version 3.19075.25 was deployed to all regions over the weekend. It contains a fix for many layout and rendering issues that were reported with last week's build.  Can you please save and re-publish your app(s) to verify if this new build resolves your issues?  Please remember it can take up to two minutes after publishing for the new version to become available for download.

If any issues persist, please let us know!

Ginevra
Level: Powered On

Re: A bug has occurred since the last version of powerapps (3.19052.19)

Hi @_Corey_ , thanks for your work. 

It seems that the problems we were experiencing before are solved, but a new, strange thing happens now. I do the following:

- Select one item in the gallery (say item A) and navigate to EditScreen

- Make some updates on one or more fields of item A

- Click Save

What should happen: the app takes one second or so to save the changes, while which the EditScreen is frozen. After that, I should navigate back to the gallery screen and see the edited item, item A, on top of the gallery list. (The gallery list is sorted on Edited, most recent on top).

Instead, before navigating, I see the EditScreen of ANOTHER item from the gallery for approximately one second. I have found out that the item shown is the one that will take the place of the previous in the gallery. For example: if item A I select is the 3rd item in the gallery list, next time item A will go up to the 1st position in the gallery list. All other items naturally move down one position. The item that shows for approx one second during loading time, before navigating back (let's call it item B), was in the old position 2, and now position 3. So the brief preview of another item is of the new item which holds position 3. 

 

I cannot see how this bug relates to my code, so I wonder if it is a loading issue not adressed in the last update?

Thanks in advance. Ginevra

Highlighted
Ginevra
Level: Powered On

Re: A bug has occurred since the last version of powerapps (3.19052.19)

Hi again @_Corey_ ,

 

The bug mentioned above (observed in the test-App) has also appeared in the app in production, even though we reversed it to its May-version. How is this possible? What can we do to avoid it?

PowerApps Staff _Corey_
PowerApps Staff

Re: A bug has occurred since the last version of powerapps (3.19052.19)

@Ginevra It sounds like the gallery may not be preserving the selected item after the data source is updated.  Do you navigate back immediately after calling SubmitForm()? or do you navigate back from OnSuccess?

Other customers have had success by navigating to the edit screen with a context variable.  For example, from the gallery screen, the navigate formula would like like this:

 

    Navigate(EditScreen, Cover, { selectedItem: Gallery.Selected })

 

 or, for the original record:

 

    Navigate(EditScreen, Cover, { selectedItem: Lookup('DataSourceName', ID = Gallery.Selected.ID) })

 

And then the edit form would be connected to this context variable--i.e. EditForm.Item = selectedItem--instead of connected to Gallery.Selected.

Ginevra
Level: Powered On

Re: A bug has occurred since the last version of powerapps (3.19052.19)

Hi @_Corey_ ,

Thank you so much for your reply. You were correct, it seems that a context gallery works better than Gallery.Selected. I did the modifications that you suggested and now it is exactly as it is supposed to be! 🙂 I just don't understand why... I read in some whitepaper that it is good practice to avoid sending context variables over from a screen to another. Should I use a context variable in these scenarios anyways?

 

I need to use Patch instead of SubmitForm, so I need to navigate in the same command where the Patch is. In general, would you say that it is safer to set Navigate() in the Form.OnSuccess?

 

Helpful resources

Announcements
thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

Top Kudoed Authors
Users Online
Currently online: 406 members 5,758 guests
Please welcome our newest community members: