Button double clicks causing multiple flow runs

[HariniParthiban]

I added a variable to disable the button right after it is clicked in order to prevent multiple flow runs. This works good when tested on development environment but fails when it goes to actual users with loads of data on the app. I doubt the button takes few seconds to be disabled within which the flow is triggered multiple times. 

Will adding a loading spinner after button click, a better idea? I'm using SQL Server as my datasource. Any suggestions will be much appreciated

[WarrenBelz]

Hi @HariniParthiban ,

How are you disabling the button ? If you set a Variable at the start of the OnSelect code

UpdateContext{{varStop: true})

then the DisplayMode of the button

If(
   varStop,
   DisplayMode.Disabled,
   DisplayMode.Edit
)

and at Screen OnVisible (or anywhere else you needed to reset it

UpdateContext{{varStop: false})

it should do the job

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

MVP (Business Applications)   Visit my blog Practical Power Apps

[DBO_DV]

Hey @HariniParthiban , 

Using a loading spinner or Navigating away to a Succes screen will definitely help. 

But the navigating away has to be the First action inside the OnSelect. Power apps works in sequence. that means that one Function is run after the other. If you make this: 

Flow.Run(); Navigate()

You will navigate away only after the flow has been triggered (or has answered to Powerapps). Giving the user the possibility to select the button multiple times.

If you use it like this:

Navigate();Flow.Run()

The user gets navigated directly to the next screen and after that the flow will be triggered. Making it impossible to trigger the flows multiple times. 

you can also add a timer that navigates the user back automatically to the previous screen after several seconds. 

[HariniParthiban]

Hi, Thanks for your comment

I'm setting a variable on the button onselect,

Disabling the button:

Resetting it on the onvisible property of the screen:

Screenshot of flow triggers with same data:

[HariniParthiban]

Thanks for your comment. I will definitely try navigating the user to landing screen before calling the flow.

[DBO_DV]

@HariniParthiban , I just saw your response to @WarrenBelz . 

seems that your code is already in the correct sequence. could you maybe just share the code that Triggers the Flow? Just to make sure, that the code is not triggering the Flow multiple times instead of the user.

[WarrenBelz]

@HariniParthiban 

I am a bit confused with the rest of your DisplayMode code - it seems to be a filter of some sort.

[HariniParthiban]

Set(

    DisposalConfirmClicked,

    true

);

ClearCollect(

    DisposalCollection,

    {

        VEHICLE_ID_FW: Lbl_Unit_Value_7.Text,

        ALERTID: varAlertID,

        ASSET_FW: Lbl_AssetSoldAlready.Text,

        ASSETCOND_FW: Lbl_ConditionDone.Text,

        METHOD_OF_SALE_FW: Dd_MethodofSale.Selected.Value,

        SOLD_PRICE_FW: If(

            IsBlank(Txt_Amount.Text),

            Lbl_Zero.Text,

            Value(Txt_Amount.Text)

        ),

        SOLD_RECIPIENT_FW: Txt_SoldTo.Text,

        SALE_PRICE_BOOKRV_FW: If(

            IsBlank(Txt_FMV.Text),

            Lbl_Zero.Text,

            Value(Txt_FMV.Text)

        ),

        VEHICLE_STATUS_FW: If(

            Dpd_AssetSoldAlready.Selected.Value = "Yes",

            "SALE IN PROCESS",

            Lbl_Status.Text

        ),

        SOLD_RECIPIENT_FW_Name: Txt_NAME.Text,

        FMV_QUOTED_BY_FW: Txt_QuotedBy.Text,

        SAPINVOICE: Txt_SAPInvoice.Text,

        FIXED_ASSETS_ID_FW: Txt_FixedAssetID.Text,

        DATE: Today(),

        CreatedBy: UserName,

        CreatedDate: Today(),

        Purchaser_Address: PickupAddress.Text,

        Purchaser_City: pickupCity.Text,

        Purchaser_State: Dd_PickupState.Selected.Value,

        Purchaser_Postal: PickupZip.Text,

        InvoiceCopy: Checkbox1_8.Value,

        RECORD_NUMBER_FW: Lbl_RecordNumber.Text,

        Email: Lbl_Email.Text,

        BookValue: Txt_BookValue.Text,

        Role: Lbl_Role.Text,

        COSTCENTRE_FW: If(

            IsBlank(Lbl_PlantNo.Text),

            Lbl_Branch_PSFT.Text,

            LookUp(

                CUSTOMERS_FW,

                SAP_PLANT_FW = Lbl_Branch_PSFT.Text,

                CUSTOMER_FW

            )

        ),

        Region: Region.Text,

        Division: Division.Text,

        Branch: Lbl_BranchName.Text

    }

);

BranchManagerDisposalConfirm.Run(JSON(DisposalCollection)); //Flow Trigger

If(

    Value(Txt_BookValue.Text) <= Value(50000),

    Notify(

        "Your request for Asset Disposal has been recorded and email has been sent to team",

        NotificationType.Success

    ),

    Notify(

        "Your request for Asset Disposal has been recorded and email has been sent to Division Manager for further approval",

        NotificationType.Success

    )

);

Navigate(

    Scr_AssetLanding,

    ScreenTransition.UnCoverRight

);

Set(

    ResetControls,

    false

);

[HariniParthiban]

Yes I'm disabling the button also on some other criteria based on User role:

Here is the code snippet:

If(DisposalConfirmClicked,

    DisplayMode.Disabled,

    DisableControls

    && !IsBlank(

        LookUp(

            USER_DEFINED38_FW,

            BRANCH_MANAGER_EMAIL_FW = Lbl_Email.Text

        )

    )

    && BranchManagerEmail_1.Text = Lbl_Email.Text

    && ManagerRole = "BRANCH MANAGER"

    && !IsBlank(

        LookUp(

            USER_DEFINED27_FW,

            UNIT_ID_FW = Lbl_Unit_Value_7.Text && TYPE_DESCRIPTION_FW = "DISPOSAL" && USER_TYPE_DESCRIPTION_FW = "BRANCH MANAGER" && USER_ID_FW = UserID,

            STATUS_FW = "ON"

        )

    )

    && !IsBlank(BranchManagerEmail_1.Text)

    && !IsBlank(

        LookUp(

            ACCESS_FW,

            EMAIL_FW = BranchManagerEmail_1.Text

        )

    ),

    DisplayMode.Edit,

    DisplayMode.Disabled

)

[WarrenBelz]

@HariniParthiban ,

This is the only way I can think of to immediately disable the button after pressing. Technically it should work but the sheer volume of both of those formulas may cause some delay in execution.