Create Reusable Confirmation Pop Up in Power Apps using Component library,, is this possbile?

[johnjohn123]

I am working on a large Power apps, and for every screen (we will have around 50 screens), we need to have a confirmation popup for deletion. but i do not want to add 50 confirmation popup inside the screens.. i found this video for creating a Popup using component library,, but the issue is that it uses an experimental feature @ https://www.youtube.com/watch?v=SfxNHYvCgcw&pp=ygUfcG93ZXIgYXBwcyBNZWRpYSBsaWJyYXJ5IHBvcCB1cA%3D%3D .. and currently the name of the options vary.. so now we do not have something called "Behavioral" .. so can anyone advice on the best way to create one Popup that i can reuse among multiple screens?

Thanks

[FLMike]

Hi @johnjohn123 

If you want something that is re-usable, you are to add it to each screen. Components themselves, have to exist on the screen before you can make them visible on the current screen.

There is no "generic sits outside as a single thing" and you said you don't want to add 1 per screen.

Components are super easy to create, but you will need to put it on each screen.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[Kirkby]

Hello @johnjohn123 

https://powerapps.microsoft.com/en-us/blog/enhanced-component-properties/

As the page above indicates, Microsoft has renamed 'behavior' properties' to 'Events.'

(I believe that an experimental phase is a step in the process leading to the General Availability (GA) and The likelihood of deprecating the feature is low because It is a core feature for creating components.)

The YouTube tip you mentioned seems to offer limited options, displaying only 'OK' and 'Cancel.' (Of course, using a popup with 2 buttons could be enough for many occasions). However, there could be more options that a user might need to select, depending on the context of the screen, such as 'OK/Cancel/Confirm/Skip/Print/Approve/Return/Delete/Restore/...Many other actions....' Instead of directly defining the types of buttons that a user can choose within the component, it would be more practical to allow the component to accommodate all possible choices you design.  

In my case, I typically add properties to distinguish each action. An example is...

SelectedAction is used to distinguish each action performed by each button you create on the pop up window.

when creating pop up window with 4 buttons. 

UpdateContext(
{tblButtonsInfo: //define buttons for screen, button options are different depending on a screen
Table( //Pop Up window component uses below properties to populate buttons, "Do Action1", "2", "3"....and "Cancel"
{
Name: "Do Action1", //This is just a text to be displayed on the button. 
Action: "ACTION_COMMAND_1", //I use a constant style to distinguish each type and avoid conflicts in cases where 'Name's are duplicated.
Order: 1,
Other properties for look & feel
},
{
Name: "Do Action2",
Action: "ACTION_COMMAND_2",
Order: 2,
Other properties for look & feel
},
{
Name: "Do Action3",
Action: "ACTION_COMMAND_3",
Order: 3,
Other properties for look & feel
},
.................
{
Name: "Cancel",
Action: "CLOSE_WINDOW",
Order: N,
Other properties for look & feel
}

)
}
);

Inside the OnSelect property of the component you created(Added) from the custom component.

Switch(SelectedAction, //Check the hidden constant behind the button that a user clicked.
"ACTION_COMMAND_1", Action that you want,
"ACTION_COMMAND_2", Action that you want,
"ACTION_COMMAND_3", Action that you want,
"CLOSEW_WINDOW", UpdateContext({blnShowDlg :false} );

I hope this  helps. (If this is not what you were asking, I seek your understanding)

[FLMike]

@Kirkby 

The experimental phase is what you said, but that feature we GA'd a long while back.

I think the big thing @johnjohn123  didn't want is to have to put it on every screen. Creating the component is easy, but still needs to be on each screen.

Lovely walk through!!! @Kirkby  How the heck do you do emojis around here lol. 🙂

[Kirkby]

@FLMike . I am afraid that I misunderstood. As you explained, there is no way as of now except adding component to each screen because there are no visual items that fly between screens.

[johnjohn123]

@FLMike i know what i will need to add the component library to each screen.. but atleast modifying the component library will get reflected inside all the screen which is fine.. but i am asking about creating a reusable popup.. yuor answer is not related to my question. thanks

[johnjohn123]

@FLMike no i know that i need to add component library to each screen which is fine, since this is what power apps offers to us...

[johnjohn123]

@Kirkby no you did not misunderstood ,, your reply in what i am looking for.

[johnjohn123]

@Kirkby thanks for the reply..so to be able to have a reusable popup we will need to use an experimental feature,... so is this fine for PROD app? 

[Kirkby]

@johnjohn123 

Hi. If you are concerned about the reliability or stability of the feature, you don't need to worry. If it's about the feature being deprecated, the likelihood is very, very low, as it would cause a significant number of PROD apps in the world to stop working if the feature is deprecated.

The very positive aspect is that MS Power Platform teams keep upgrading features when they find something that needs to be revamped through experimental stage. (I am not a spokesperson of MS 😅)

@FLMike  Hi. I don't know if I am too optimistic in my belief. 😄 My understanding is that Enhanced component properties are still in the Experimental tab just like JohnJohn123, and I see it in the settings. ('https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/component-properties.') I need your advice. Are update rings for Power Platform applied in the same way as M365 apps like Teams? Could there be differences in ring policy settings by a user? Thanks!!