Unanswered

SharePoint list form - navigate to a different screen on startup based on column value

(0) Share

Report

Posted on by blanghorst

206

Is it common to have to continuously refresh your browser after every access of a PowerApps form? It seems like forms are being cached and you have to manually refresh an inordinate amount of time for the forms to work correctly.

I have a form which is supposed to navigate to a specific screen on startup based on a SharePoint list column value. If I click a line item which has a "Pending" status, it is supposed to open the app on the "Pending" screen. If I click on a line item which has an "Assigned" status, it is supposed to open the app on the "Assigned" screen. Assuming this works correctly, I can click on the Pending item, it shows the Pending screen, and then when I click on the Assigned item, it shows the Assigned screen. The issue is that when I then click the NEW button on the list, I don't get the New view - it shows me whatever the last form was. For example, if I clicked the Assigned item first, closed it, and then clicked the New button, the form would open on the Assigned screen until I manually refreshed the screen. Why is this happening? The rules are below - please help me.

OnStart of default screen: Set(varStatus,SharePointIntegration.Selected.'Status'.Value);If(varStatus="Pending",Navigate(Pending,ScreenTransition.None));
If(varStatus="Assigned",Navigate(Assigned,ScreenTransition.None))

SharePointIntegration:

OnNew: NewForm(SharePointForm1)

OnEdit: Set(varStatus,SharePointIntegration.Selected.Status.Value);If(varStatus="Pending",Navigate(Pending,ScreenTransition.None));
If(varStatus="Assigned",Navigate(Assigned,ScreenTransition.None))

OnView: Set(varStatus,SharePointIntegration.Selected.Status.Value);If(varStatus="Pending",Navigate(Pending,ScreenTransition.None));
If(varStatus="Assigned",Navigate(Assigned,ScreenTransition.None))

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

v-sheyu-msft on at

Like (1)

Report
hi @blanghorst,

I made a test. The same issue reproduce on my side.

you can try to set OnNew property of SharePointIntegration to:

ResetForm(SharePointForm1);NewForm(SharePointForm1);Refresh(test)

regards,

eason

Was this reply helpful? Yes No
blanghorst 206 on at

Like (0)

Report

Thanks, but I am still seeing the issue even after implementing your suggestion. Let me give an example to illustrate my problem.

SCENARIO: I have a form with 3 screens: New, Pending, Assigned. There is a column called Status which should allow the form to route to the proper screen on form load and I've applied those rules on both the OnEdit and OnView properties of the SharePoint integration - if Status=Pending, the form should open on the Pending screen; if Status=Assigned, the form should open on the Assigned screen.

1. If I navigate to the site and click NEW on the list toolbar, a new form opens without issue. I click X to close it.
2. If I click on an existing item in Pending status, the form opens on the Pending screen. If I click on a form in Assigned status, the form opens on the Assigned screen.
3. If I click X on a Pending or Assigned form and then click the NEW button, it launches in the previous screen - for example, if I had a form open on the Pending screen, closed it, and clicked NEW, the form opens on the Pending screen.
4. If I manually refresh the site and THEN click NEW, it opens in the NEW view as expected.

Even opening in the "Pending" or "Assigned" screens isn't always consistent; sometimes I'll have to click on a "Pending" or "Assigned' form a couple of times before it opens in the right view. This is completely and totally unacceptable - I can't tell users to click on things twice, nor can I tell them they'll need to remember to manually refresh a screen every time they close a form and before they open a new form. I REALLY need this to work and work reliably - any other suggestions? I've attached a screenshot showing my new rules.

PowerAppsScreenRo...

Was this reply helpful? Yes No
blanghorst 206 on at

Like (0)

Report

Any thoughts?

Was this reply helpful? Yes No
blanghorst 206 on at

Like (0)

Report

Any additional thoughts? How can this be happening in two separate environments, you can reproduce it easily, and yet no one can really determine the issue?

Was this reply helpful? Yes No
blanghorst 206 on at

Like (0)

Report

So, months later, no one can help me with this issue? The summary:

1. I open a form - let's call it FORM1. Let's say it routes to the Pending screen. I use the X button to close it.
2. I click on another form in the list - let's call it FORM2. FORM1 opens. It is clearly cached or something, because the rules aren't processed.

HOW CAN I PREVENT THIS? Come on Microsoft, this is ridiculous - you said you could reproduce it.

Was this reply helpful? Yes No