Unanswered

Navigate Function stop to works on update from 3.25031 to 3.25032

(1) Share

Report

Posted on by pl_Rocha

Hello.

I have an app that I’ve been developing for four months. Today, some tester users noticed that the function to navigate to two different pages stopped working. I haven't made any changes to these buttons in the past few weeks, but I have modified other parts of the app. These buttons work normally when I'm in editing mode. But not in the published version.

The only difference I noticed was the Authoring app version changing from 3.25031 to 3.25032. Restoring version 461 of the app (the last working one) and publishing it makes the buttons work again. However, any change I make to the app, even reverting the authoring version to 3.25031 before published, causes the functions to stop working. I also tested it with version 3.25033.9 with the same results.

The only similarity between these buttons is that they pass parameters to the pages, whereas the other buttons do not.

I’ve tried everything to make the functions work again, even downloading and re-uploading the app, but without success. Only these two functions are not working.

The only thing that worked was disabling the New Analysis Engine, but the app uses several UDFs.

In the Live Monitor the behavior of the Published and Edit APP are very diferente. The publisher app monitor log is attached (action to click on the button).

Any solutions for this issue?

Categories:

Experimental features

PowerAppsTraceEve...

I have the same question (0)

All responses (6)

Answers (0)

Michael E. Gernaey 53,433 Super User 2025 Season 2 on at

Like (0)

Report

Hi @pl_Rocha

Thank you for posting, however I do not see any code to review or visualizations that show the data flow. Please show the expressions in the buttons, the explanation of how it works, how data is set or whatever you are doing, and explain what it should do.

Are there variables or anything that it relies on, or is it in a gallery and etc etc.

Was this reply helpful? Yes No
pl_Rocha 11 on at

Like (0)

Report

Hi @Michael E. Gernaey.

The code is very simply and was unchanged for at least 1 month.

The On Select event of a Moderns Button:
Button 1: Navigate(scr_Novo_Kaizen,ScreenTransition.Fade,{lvarReset:true})

Button 2: Select( Parent );Navigate(scr_Editar_Kaizen,ScreenTransition.Fade,{lvarID:Int(ThisItem.Value.ID),lvarLoaded: false })

It's just related with the Authoring version... If i change back to an older version, like the 3.25023.8 the button come back to life again.

Was this reply helpful? Yes No
Michael E. Gernaey 53,433 Super User 2025 Season 2 on at

Like (0)

Report

And neither button works at all, or neither button works randomly and let's get more detailed oriented here.

Button 1 on items A, it never ever works, or it sometimes works but you gotta press it 10 times, or you move around different screens and come back and omg it works.

Explain better to us what you tried, it is too difficult to go back and forth giving suggestions on common things to do.

What values are properties you are trying to pass during runtime.

that you for showing the trace, but I dont download stuff from people, so summarize what you added to the Traces so you could validate the data, and also did you do any filtering in Monitor for errors and if so what did you find?

Was this reply helpful? Yes No
pl_Rocha 11 on at

Like (0)

Report

Only these two buttons don't work at all, you click on them and nothing happens. All other still fine.

On the versions 3.23031.10 when i upgrade from an older version the buttons work, but when downgrade from a newer version they don't. This when i publish the app, on the edit still fine in all versions.

I'm using the 3.25023.8 for now, but this version will be discontinued on the future.

Was this reply helpful? Yes No
GREGWOUARE 39 on at

Like (0)

Report

Dude you're lucky it still works in this version, I had to fall back down to 3.25024.11 to find back the normal usage of my app !!

Was this reply helpful? Yes No
pl_Rocha 11 on at

Like (0)

Report

Any suggestions? Now my app can't be updated because i run out of versions without this issue.

Was this reply helpful? Yes No