Great post - Not too sure whether I have done something wrong, or there has been an update in versions. However, for the life of me I can not get the MultipleOpen to fire and close all the other items. I had to fiddle with the AccordionControlContainer height so that if ItemExpanded, then use the Content detail, otherwise use the Header detail; otherwise even though the content was not visible, it still accounted for the space being used, and as I had mutliple lines of text it left big gaps between each item.
Just an update after posting, I cut and paste the formula and the multi open seemed to work - my work around for the height of the content was still required, but I will try again as you never know with PA if it has itself all confused
Thanks for bringing this to my attention. It seems a recent update might have broken how the Auto Height property updates within components. The reason the original formula worked to calculate the height of the AccordionControlContainer was because the height of lblContent and containerContent would be 0 while invisible. It seems now when you're on the component screen, lblContent has a height of 20 with Auto Height enabled. It should be working when inserted on an actual screen though in my testing. Did you experience the same thing when inserted on a screen or did it work properly? Thanks!
Hello! There are some tricks you can use in the new modern icon/button controls to add an animation, but the animations unfortunately aren’t very smooth in Power Apps. I’ll post an update if I have a solution for you!
Nice video mate! have you tried the creator kit components yet? I just spent about 300 hrs making a template out of them for my app developers, might knock up a video myself soon to demo them. P.s. a shorthand version of your multipleOpen could be "If(MultipleOpen,Update(colItems, {ItemExpanded: Heading=ThisItem.Heading})" - just reset every property to false except the selected one, the compiler will probably run it faster than the updateif version too! :)
Thanks for your comment! I've used the creator kit components in a lot of projects over the past couple years. It's a great set of components and they've definitely done some great work! I've started to move away from them for a couple reasons, mainly due to: 1. The modern controls taking the focus for the Power Apps dev team and 2. Due to the creator kit components being the original fluent design. Microsoft is just now rolling out Fluent 2 design in a lot of their online applications, so to align my Power Apps with the experience that users see in other areas of Microsoft 365, I've started to move to these Fluent 2 components that utilize the modern controls. I like your suggestion of using an Update function for accounting for the multiple open property. I think the reason I didn't go this route is because the Update function would replace the entire record with the value specified, so using that formula would delete your heading and content text from the collection unless you also included that in the Update function. I'm going off of memory so I might be wrong on that. I'll give your suggestion a shot and see how it works out 😊 I'll keep an eye out for that video on your template app for the creator kit controls! It sounds really interesting and even as someone using the controls there are always new things to learn and new ways to use them. Thanks!
Awesome, thank you so much!
Awesome video dude, can't wait for the next upload!
Glad you liked it!! More to come before the end of the year 😎
Great post - Not too sure whether I have done something wrong, or there has been an update in versions. However, for the life of me I can not get the MultipleOpen to fire and close all the other items. I had to fiddle with the AccordionControlContainer height so that if ItemExpanded, then use the Content detail, otherwise use the Header detail; otherwise even though the content was not visible, it still accounted for the space being used, and as I had mutliple lines of text it left big gaps between each item.
Just an update after posting, I cut and paste the formula and the multi open seemed to work - my work around for the height of the content was still required, but I will try again as you never know with PA if it has itself all confused
Thanks for bringing this to my attention. It seems a recent update might have broken how the Auto Height property updates within components. The reason the original formula worked to calculate the height of the AccordionControlContainer was because the height of lblContent and containerContent would be 0 while invisible. It seems now when you're on the component screen, lblContent has a height of 20 with Auto Height enabled.
It should be working when inserted on an actual screen though in my testing. Did you experience the same thing when inserted on a screen or did it work properly?
Thanks!
@@PowerAppsGuy Thanks for getting back to me - I think it still affected my component while on the screen, so I went back to my work around
The fluent 2 of the accordion has an animation - any chance I could get that animation as well? 🙂
Hello! There are some tricks you can use in the new modern icon/button controls to add an animation, but the animations unfortunately aren’t very smooth in Power Apps. I’ll post an update if I have a solution for you!
Nice video mate! have you tried the creator kit components yet? I just spent about 300 hrs making a template out of them for my app developers, might knock up a video myself soon to demo them. P.s. a shorthand version of your multipleOpen could be "If(MultipleOpen,Update(colItems, {ItemExpanded: Heading=ThisItem.Heading})" - just reset every property to false except the selected one, the compiler will probably run it faster than the updateif version too! :)
Thanks for your comment! I've used the creator kit components in a lot of projects over the past couple years. It's a great set of components and they've definitely done some great work! I've started to move away from them for a couple reasons, mainly due to:
1. The modern controls taking the focus for the Power Apps dev team and
2. Due to the creator kit components being the original fluent design. Microsoft is just now rolling out Fluent 2 design in a lot of their online applications, so to align my Power Apps with the experience that users see in other areas of Microsoft 365, I've started to move to these Fluent 2 components that utilize the modern controls.
I like your suggestion of using an Update function for accounting for the multiple open property. I think the reason I didn't go this route is because the Update function would replace the entire record with the value specified, so using that formula would delete your heading and content text from the collection unless you also included that in the Update function. I'm going off of memory so I might be wrong on that. I'll give your suggestion a shot and see how it works out 😊
I'll keep an eye out for that video on your template app for the creator kit controls! It sounds really interesting and even as someone using the controls there are always new things to learn and new ways to use them. Thanks!
That'd be awesome if you did! I'd watch it!