What is the Plan: ENHANCED COMPONENT PROPERTIES

[nagarjunaking]

Enhanced Component Properties has been experimental since Feb 2021, last updated in June 14, 2023 & been 10 months since.

In my opinion, this is a critical functionality of components and needs to be released which creates a lot of usecases & REUSABILITY.

Looking for feedback from Microsoft on the current plan for this feature?

 Joris de Gruyter, Senior Program Manager mentioned below @JorisD 

"We are not intending to make any more feature changes at this time, and are purely focused on pushing this set of features to a generally available state, with quality. We are looking forward to your feedback and any issues you may find. You can engage with our team on the Experimental Features forum."

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

[ShantanuP · Accepted solution]

We are working on fixing last few issues in this feature. Once those are done, we plan to move this out of experimental state soon.

[nagarjunaking]

Thanks for the response Shantanu. I'm waiting for this feature from along time & it's a gamechanger for reusability & other usecases.

[claytsch]

Can you provide feedback on some of the issues that are being worked on?  I don't see anything related in upcoming releases.  This feature has been experimental for 3 years.  This feature is very powerful a must for complex apps but I do still have some issues implementing them efficiently. 

The biggest 2 issues I have are:

1. Nested Records/Tables can't be referenced properly in components.  Some of my components have dozens of properties so I use record properties to store nested properties to things organized and not have to scroll through dozens of component level properties.  <Component>.Header.[Layout] vs <Component>.[HeaderLayout].  When I reference the nested table, some controls don't recognize the table or throw errors or don't refresh when the Property is updated.  When I add a specific table property at the component level, it can be reference properly.  PowerApps would be much easier to manage if nesting properties/controls was allowed for referencing instead of unique names.  i.e.  Screen1.Header.Title and Screen2.Header.Title instead of Screen1HeaderTitle and Screen2HeaderTitle.

2. When a Property type or record/table schema is changed, the existing set value is cleared.  When I have dozens of instances of a component, and need to update the property I have to copy the existing value from dozens of components before updating the property then paste the previous values back after.