Reading Variables of Multiple Instances of a Component on Same Form

[eauerbach]

I'd initially built out the alpha-version of an app to get user feedback and settle on functionality. It's basic in its structure and I used all OOB components. A major feedback item has been that the stock look is not very good and I'm now redesigning the app to match our company branding. To make supporting the app going forward easier, I've been creating custom components to reuse on the forms, and am finding them very easy to work with and deploy. However, I've run into an issue on one form where I'm reusing a component for section expansion/collapsing. Very simple component with OnSelect setting a variable to true or false to expand the items below it:

Expanded is exposed by the output parameter IsExpanded:

I'm reusing the component 5 times on a form. When I added the section component and wired it to its associated items visibility properties, each section responded correctly.

When I navigated away and came back, only the last section responded to the boolean change. Is this a limitation of components that they cannot have multiple instances on the same form? If not, how do I get the items to recognize the updated value?

[v-yutliu-msft]

Hi @eauerbach ,

Do you mean that your variable value in components can not change with the variable?

Yes, it is a known issue. I've reported this to our product team.

Thanks for your feedback!

Here's a similar issue, if there's any reply about this, I will leave message there:

https://powerusers.microsoft.com/t5/Building-Power-Apps/Reusable-componant-bug/td-p/473253

Best regards,

[Mr-Dang-MSFT · Accepted solution]

Hi @eauerbach,

If you were experiencing issues involving variables and components, it might be the one we rolled out a fix for earlier today. If that is the case, can you let us know if the issue is resolved for you?

If that is not the case, can you describe more context around your setup?

[eauerbach]

Yes, this seems to be resolved. The individual sections are expanding with respect to the clicks. I have a secondary issue with the same control that the text input is not reflected, but I'll address that separately from this thread.