Power Platform Community Forum Thread Details

Hello my dear community

I have the following problem:
I have a big SharePoint List of >120 fileds and a PowerApp who is utilzing that list with 6 Screens.
The problem is now, that some users (not kids) are saving the same item 4 times..., unbelivable but it so.
The save button OnSelect is roughly as follows:

Patch()-Function //saving all screens to the same time
Notification() Function  // Is informing the user that the data is saved
Navigation() Function  // is navigating to the landing page

The following 4 possibilities are known:

(1) I change the order to: Notification(), Patch() and Navigation()
     The problem is, that user are not getting really the notify() information on the top of the app screen.
     And an error who is trown could create missleading reactions.

(2) I use SubmitForm(Screen1) and then for all other screens Screen1.LastSubmit.
     The problem is, that the user can't cancel the new item anymore on any screen because on the first screen1 data is saved.
      And the following save buttons on each screen are only the Update of the new existing item in the list.

(3) I use a label field to block the button by using the following:
     App.OnStart: Set(varShow,false)
  ButtonSave: OnSelect
  Patch()
  Notify("Your data was saved...",NotificationType.Success);
  Set(varShow,true);

    The good part is: I can see the button because the label who is over the button is white but alpha is 40% only
                                It is not possible not to use the button because the label is blocking it.

For demonstartion purpose I have used a text and border in that label:

(4) I use visible on the button, but the weird part is, the button is disappearing...

The question is now: "Is there any other idea who makes sense and is maybe the best approach by having a spinning spin who blocks the whole screen at saving?"

The problem is, that most user needs a fast feedback and but if the app is to big, then you will get the following slow points:

(1) The amount of data to save is to high
(2) The data connection to the cloud is to weak
(3) Microsoft is doing updates or having cloud issues:"The black box"

So if somebody has a very reliable idee that will most appreciated ;)

The other question is, if the sequentiell steps going to the commands is fast, because if the PATCH() funktion troughts an exception nothing will happen.
But if there is no exception, is there a time limit for that kind of exception and if the saving is happen in the cloud is the next step: "Label blocks Button" is possible at that time?

STEPS are:
Patch();
Notify();
Set(labelView, true);

Thanks in advance for any ideas ;)

I wish a nice day.

Kind regards
Michael

Categories:

Power Apps component framework

Application Lifecycle Management (ALM)

Power Platform Build Tools