Complicated PowerFX Formula Causing Unexpected Navigation Behavior

[memtech3]

I am developing a PowerApps canvas app with SharePoint Lists as the back end. I had developed a proof of concept with Dataverse as the back end but came to the conclusion that it would cost more to use Dataverse as the back end and decided to switch to SharePoint Lists.

The below formula is in the OnSelect field of the submit button and is used to stop the submission of a form if the system pressure field deviates from the average value of all inspection records (inspections list) that have the selected well (SharePoint List lookup field that references Wells list) by more than 15% unless the user has enabled the pressure override switch.

If(
    Not(Abs(Value(DataCardValue8.Text) - 
     Average(Filter(Inspections,Well.Id = DataCardValue6.Selected.Id),'System Pressure')) > .15*Average(Filter(Inspections,Well.Id = DataCardValue6.Selected.Id),'System Pressure')) 
    Or DataCardValue7.Value
    , SubmitForm(EditForm1); Navigate(PostInspectionScreen, None),
    Notify("System Pressure Above Acceptable Level", NotificationType.Error)
    )

When used with Dataverse as the back end, the app would proceed to the PostInspectionScreen. With SharePoint as the back end, it briefly shows the PostInspectionScreen but then quickly goes back to the edit form. When I remove the formula and replace it with Navigate(PostInspectionScreen, None) the button functions properly.

I'm not quite how to squash this bug as I don't have much experience with PowerApps or SharePoint. The first thing that comes to mind is that I'm asking too much of SharePoint. If that's the case, is there a way to request only the last two records?

Below are some screenshots of my environment

[memtech3]

I'm not sure what you're referring to

[WarrenBelz]

This in your code

Notify(
   "System Pressure Above Acceptable Level", 
   NotificationType.Error
)

also put this on a label - does it show true or false ?

With(
   {
      wAve:
      With(
         {
            wList:
            Filter(
               Inspections,
               Well.Value = DataCardValue6.Selected.Value
            )
         },
         Average(
            wList,
            'System Pressure'
         )
      ),
      wVal:Value(DataCardValue8.Text)
   },
   !(Abs(wVal - wAve) > (wVal * .15)) || DataCardValue7.Value
)

[memtech3]

Oh! That thing right. When I set the pressure to an acceptable level I do not see the notification and it briefly shows the Post Inspection screen. When I set the pressure to an unacceptable number I see the notification and it does not attempt to switch to the next page.

[memtech3]

The label shows true when the pressure is in the acceptable range and false when it is outside of the acceptable range.

[WarrenBelz]

This is a logic problem, not a coding item. The code we have now works in a manner you can predict, so you just have to set the actions - to summarise your code

If( 
   <Your pressure is true - and that works >
   SubmitForm(EditForm1);                       //submit the form
   Navigate(PostInspectionScreen, None),        //and navigate to the next screen 
   Notify(                                      //OR notify pressure is wrong and stay on the screen
      "System Pressure Above Acceptable Level", 
      NotificationType.Error
   )
)

now we have established the code is working in the true/false test, we can move on to the workflow - what exactly is it doing other than the above ?

[memtech3 · Accepted solution]

I found the issue! Instead of calling navigate in the onselected of the button, I needed to change the onSuccess value of the form. 

https://powerusers.microsoft.com/t5/Building-Power-Apps/Return-to-different-screen-after-submit-form.... Duplicate of the issue linked above

[WarrenBelz]

@memtech3 ,

After all of that you accepted your own solution  . . .  ?

[memtech3]

Your help in diagnosing the issue was greatly appreciated however another thread existed that had information most relevant to solving this problem so I linked it and marked it as the solution so that other users reading this thread could quickly jump to that thread.

[WarrenBelz]

@memtech3 ,

It would have been good if you had found that much earlier . . .