Create Reusable Confirmation Pop Up in Power Apps,, is this possible?

Steel Contributor

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

7 Replies

@john john 

 

You should be able to create a reusable confirmation pop up using the components in Power Apps.

 

If you are going to use the component in this single app only, no need to use component library. You can create and use components directly from app.

 

If you want to have dynamic text to show on confirmation pop up, you can use input properties for your component and pass the text every time you add component to your screen -  remember you can have default value for input properties as well if same text need to be used on multiple screens.


Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.

@ganeshsanap yes i know what you mentioned... but is it fine to use an experimental feature for PROD app? my question was if there is a way to add reusable popup using none-experimental feature.. as we will be deploying our app to PRODin the next 2-3 months 

@john john 

 

Power Apps "Components" is not a experimental feature. So, it is safe to use in the production environments as well.

 

DocumentationCanvas component overview 

 

However, some of the new component properties are experimental features currently. So, you should avoid using those for production. Check: Canvas component properties (experimental)  

 

Additional ReferenceUnderstand experimental, preview, and retired features in canvas apps 


Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.

@ganeshsanap to be able to pass events to the component library we need to enable the "Enhanced component " feature which is an experimental feature:-

 

johnjohn_0-1697659368075.png

 

 

so is it fine to use this on PROD environemnt?

 

@john john 

 

Those properties are related to 2nd link (experimental component properties) given in my above response.

 

As those are experimental feature currently, you should avoid those using in production environments.

 

Microsoft may change the functionality before moving it from experimental to preview and then GA. Sometimes those can be GA as is or sometimes Microsoft can discard the feature completely as well - no guarantee really. So, don't depend on it.

 

Check (from 3rd link): 

ganeshsanap_0-1697698136573.png

Also, I am not sure about all your requirements but you may be able to create a reusable component without using these experimental component properties.


Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.

@ganeshsanap is there a way to create a reusable component without using these experimental component properties??

@john john Please read my above responses carefully.

 

It is possible but it depends on your requirements what exactly you want to do. I don't know all your requirements so I cannot confirm for sure.

 

You can pass the input properties to have dynamic text, you can also pass the code to execute via input properties.


Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.