Hi,
Adding custom properties to PowerApps components is straightforward enough. However, there doesn't seem to be a straightforward way to remove a custom property from a component if that property is subsequently no longer needed. I appreciate that if there are instances of the component in use throughout the app, deleting a component's custom property would necessarily impact component instances that make use of the deleted custom property. If however, none of the instances of a component are using a component's custom property that is up for deletion, then surely it should be possible to just remove that custom property from the component definition ? Right now, the only option appears to be deleting the entire component and recreating it minus the unwanted custom property. Have I missed something ?
@Sherwin , though it's hidden, this is the solution! Had I posted the original message I would have marked this as the solution! Thanks!
BTW, you edit the custom property by clicking on the data type of that property.
Tap on the data type in front of the component name to edit the same> scroll down and select Delete Custom Property> Delete.
As this is completely hidden, I'll elaborate. You open the Custom Property edit pane (which is where the Delete link is) by clicking on the *type* of the Custom Property in the Custom Property list.
It is not as straightforward, but you can delete a custom property if you click on the data type as opposed to the ellipses or the name of the property.
Hi @EricRegnier . The component was just a button that was intended for use on multiple screens, the idea being that it would have similar characteristics throughout the application and wouldn't have to be re-developed for each new screen.
Addding a required property and deleting a existing one is not possible currently. As you pointed there needs to be a upgrade step to manage the currently configured control which would be complex to cover all possible cases. Currently these changes are classified as breaking changes and control needs to be renamed and bought in as new control. MyPCFControlV2 for example , the control needs to be reconfigured from scratch again.
Please use ideas forum which would help us prioritize investment in the area.
hemant
Hi @flarebear , would it be possible to know what exact type of PowerApps component and/or property you are try to delete? Thanks
Edit the custom property then after the Data Type section, there is a link to Delete custom property
>Do you want to remove the custom property within the Component?
Yes, within the Component definition, rather than a specific component instance. In the PowerApps studio there is a '+' to add a custom property, but no corresponding '-' to remove it; or better still an option within the custom property options '...' ellipsis menu of a custom property to remove it.
>Do you want to remove the custom property from the Master Component without affecting other instance which use the custom property?
It is understood that removing a custom property from the Master Component / Component definition would necessarily remove it from component instances, but there appears to be no way to even do that. So to achieve that, the developer has to delete the entire component and laboriously recreate it without the unwanted custom property.
Hi @flarebear ,
Do you want to remove the custom property within the Component?
Do you want to remove the custom property from the Master Component without affecting other instance which use the custom property?
If you want to remove the custom property from the Master Component without affecting other instance which use the custom property, I afraid that there is no way to achieve your needs in PowerApps currently.
If you would like this feature to be added in PowerApps, please consider submit an idea to PowerApps Ideas Forum:
https://powerusers.microsoft.com/t5/Power-Apps-Ideas/idb-p/PowerAppsIdeas
I agree with your thought almost. If there are instances of the component in use throughout the app, deleting a component's custom property from Master Component would impact component instances.
Best regards,
WarrenBelz
81
Most Valuable Professional
mmbr1606
53
Super User 2025 Season 1
stampcoin
48