cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

How can I make the clicking of an icon change the icon itself?

I would like to make an icon's onSelect() value be something like:

onSelect(
  If(
    Self.Icon = ChevronUp,
     Set(Self.Icon, ChevronDown)
  )
)

 

...and vice versa. I basically want the clicking of the icon toggle between ChervronUp/ChevronDown. What's the best way to go about this? It seems trying this gives an error that Set() can't contain any conflicting logic. 

1 ACCEPTED SOLUTION

Accepted Solutions
RusselThomas
Community Champion
Community Champion

Hi @aec2018 ,

It helps to know you're building it inside a component as components have different rules (and a different baseline scope) than screens, so it might be worth exploring this a little before suggesting a correction.

 

Inserted components are instances of a source component object - an object whose parent is the App, but contains it's own scope - meaning it can access App properties because the App is it's parent, but it has no inheritance from or relationship to anything else that the App is parented to - like screens or collections or other objects or controls outside of the component.  This is why we have to spoon-feed component instances information using input properties.

   

This is also why you can't insert components inside Galleries or other controls that impose parent/child hierarchy - the source component is already anchored to the App as its parent, and the nature of components is to be an instance of the source component which retains that hierarchy.

   

It also means you cannot have a component inside a component, so it's not possible to "nest" components or have parent/child components - a component is a child of the App, and that's it - it cannot be a child of anything else.

 

What you have here is a container inside a component - Containers are just logical groupings of objects similar to forms with cards - but their properties are very simple.  Like any other control, you can place containers inside components, or screens, or galleries or even other containers, and they will become part of that hierarchy - so while they can be children of components, they are not components themselves.  

 

This brings us to why UpdateContext() doesn't work inside a component.

  • Placing an instance of a component inside a screen doesn't change the original components heritage - which is related to the App, not the screen.  
  • Local variables are set using UpdateContext({name: value}) and they are local to a screen context.
  • As there is no screen context to a component, this means you cannot create or anchor local/screen variables inside them, which is why UpdateContext() has no relevance inside a component.

Collections and global variables are accessible across the app, but are not accessible from inside a component.

Because of this, information must be passed in as property values.  Collections and global variables can be created inside components - but they are not accessible from the outside - these can only be passed out as output property values.  In effect, components are like mini-black-box-apps inside your app, with input and output properties being the only things you can use to pass information between them. 

 

Note: Because of this hierarchy, you cannot set an input property of a component from inside a component - it's almost like trying to pass your app a URI parameter from inside your app. 

You can however pass a value from inside the component to the App via an output property of the component, and then feed it back into the component from the App through an input property - which funnily enough sounds like a circular reference, but because components are like black boxes nothing passes through them and this actually works - although I can't say whether this is by design or by accident - either way it can make for very confusing component logic.  

 

So - how do we do this:

While collections and global variables created outside a component are not directly accessible from inside a component, you can create them inside a component.  This just means they become contained within the component - so not directly referable from the outside, but you can reference them from anywhere inside a component.

Global variables are set using Set(name, value).

While you can Set() a "global" variable inside a component, note that they are "global" only to the component context, so not truly global in the App sense - but they work inside components so....

 

Try this - set the variable on your icon OnSelect: property;

 

Set(cvarChevronToggle, !cvarChevronToggle)

 

Keep the Icon: property of the icon the same as the example I gave above.  This should toggle the icon as you click it.

You can then use the same variable cvarChevronToggle to drive other behaviour inside the component - what to do when cvarChevronToggle is true, and what to do when it's false (eg: expand/collapse)

While you could possibly pass this value out of the component as an output property and back in as an input property, I'm not sure what this would achieve at this point - I'd suggest just seeing if you can get this logic working inside the component for now, then think about how best to utilise input/output properties.  

 

Hope this helps,

RT

View solution in original post

6 REPLIES 6
RusselThomas
Community Champion
Community Champion

Hi @aec2018 ,

So as you've probably figured out already, you can't directly "set" a property on an object.  The only way to dynamically set properties is to set the property to a variable, then dynamically change the variable.

In your example, there are a few ways to do it - I'd do this;

OnSelect: property;

UpdateContext({chevronToggle: !chevronToggle})

This will set the variable chevronToggle to true when it's false and false when it's true, effectively acting as a toggle.

You can then set the Icon: property of the icon to;

If(chevronToggle, icon.ChevronUp, icon.ChevronDown)

Hope this helps,

RT

 

Hey @RusselThomas ,

 

I appreciate the help. Where would I be setting the variable? I had kind of attempted something like that on the parent component. I'm trying to build this as a reusable custom component and I set a variable on the main component itself. So in this case, cmp_Filter_DatePicker(1) has a custom boolean variable and ico_DatePicker_Filter_Expand(2) would toggle that variable in its onSelect() property. But it seems that the child component can't set anything on a parent component. Also, when I try using UpdateContext(), it doesn't seem to recognize it as a function.

 

aec2018_0-1657906421157.png

Thanks!

-Alex

RusselThomas
Community Champion
Community Champion

Hi @aec2018 ,

It helps to know you're building it inside a component as components have different rules (and a different baseline scope) than screens, so it might be worth exploring this a little before suggesting a correction.

 

Inserted components are instances of a source component object - an object whose parent is the App, but contains it's own scope - meaning it can access App properties because the App is it's parent, but it has no inheritance from or relationship to anything else that the App is parented to - like screens or collections or other objects or controls outside of the component.  This is why we have to spoon-feed component instances information using input properties.

   

This is also why you can't insert components inside Galleries or other controls that impose parent/child hierarchy - the source component is already anchored to the App as its parent, and the nature of components is to be an instance of the source component which retains that hierarchy.

   

It also means you cannot have a component inside a component, so it's not possible to "nest" components or have parent/child components - a component is a child of the App, and that's it - it cannot be a child of anything else.

 

What you have here is a container inside a component - Containers are just logical groupings of objects similar to forms with cards - but their properties are very simple.  Like any other control, you can place containers inside components, or screens, or galleries or even other containers, and they will become part of that hierarchy - so while they can be children of components, they are not components themselves.  

 

This brings us to why UpdateContext() doesn't work inside a component.

  • Placing an instance of a component inside a screen doesn't change the original components heritage - which is related to the App, not the screen.  
  • Local variables are set using UpdateContext({name: value}) and they are local to a screen context.
  • As there is no screen context to a component, this means you cannot create or anchor local/screen variables inside them, which is why UpdateContext() has no relevance inside a component.

Collections and global variables are accessible across the app, but are not accessible from inside a component.

Because of this, information must be passed in as property values.  Collections and global variables can be created inside components - but they are not accessible from the outside - these can only be passed out as output property values.  In effect, components are like mini-black-box-apps inside your app, with input and output properties being the only things you can use to pass information between them. 

 

Note: Because of this hierarchy, you cannot set an input property of a component from inside a component - it's almost like trying to pass your app a URI parameter from inside your app. 

You can however pass a value from inside the component to the App via an output property of the component, and then feed it back into the component from the App through an input property - which funnily enough sounds like a circular reference, but because components are like black boxes nothing passes through them and this actually works - although I can't say whether this is by design or by accident - either way it can make for very confusing component logic.  

 

So - how do we do this:

While collections and global variables created outside a component are not directly accessible from inside a component, you can create them inside a component.  This just means they become contained within the component - so not directly referable from the outside, but you can reference them from anywhere inside a component.

Global variables are set using Set(name, value).

While you can Set() a "global" variable inside a component, note that they are "global" only to the component context, so not truly global in the App sense - but they work inside components so....

 

Try this - set the variable on your icon OnSelect: property;

 

Set(cvarChevronToggle, !cvarChevronToggle)

 

Keep the Icon: property of the icon the same as the example I gave above.  This should toggle the icon as you click it.

You can then use the same variable cvarChevronToggle to drive other behaviour inside the component - what to do when cvarChevronToggle is true, and what to do when it's false (eg: expand/collapse)

While you could possibly pass this value out of the component as an output property and back in as an input property, I'm not sure what this would achieve at this point - I'd suggest just seeing if you can get this logic working inside the component for now, then think about how best to utilise input/output properties.  

 

Hope this helps,

RT

Hey @RusselThomas ,

 

Ah, thanks for the great in-depth explanation. That really explains a lot of the scope headaches I was dealing with when making these custom components. I went ahead with your suggestion and then set the visibility of the cntr_Datepicker_Filter to the value of the Icon with an If() statement and it worked!

 

 

Icon changing on clickIcon changing on click

 

I'm curious how this worked, though. One of my problems has always been wondering where I have to establish a variable. For instance, cvarChevronToggle in this scenario. Where you're suggesting that I declare it in the onSelect() property, does using Set(var, !var) automatically 1)instantiate that variable and 2)as a Boolean automatically? I was thinking I had to set it somewhere first which is why I was setting it as a custom variable on the custom component itself. 

 

This really helps, by the way. It was a real headache since I felt it was possible but the circular logic was really blocking me. This is exactly what I was looking to do.

 

-Alex

RusselThomas
Community Champion
Community Champion

Hi @aec2018 ,

Glad to hear it 😊

Variables (and fields in tables, collections or records) become typed the first time they are assigned a value - so whatever you assign them the first time is what they become typed as.  So yes, assigning it a value of !variable does two things;

Firstly the ! operator is the equivalent of Not() which results in a boolean, thereby typing it as boolean.  On first load, all boolean variables evaluate to false by default - so the first click would make it Not(false) which is equal to true - thereby typing it as boolean by assigning it a true value.

Secondly, every time you click, you're setting it to Not(itself) so each click will make it the opposite of what it currently is - i.e. true/false.

Hope this helps,

RT

 

Hi,

 

I have created one component, when i click on chevron icon, it will expand and show gallery and when i clicked it again it will collapse and hide the gallery. but my requirement is when i expand the icon it needs to show gallery and if i click anywhere in screen, the gallery needs to be hide and chevron need to be collapsed instead of clicking that icon again for closing the gallery. Any idea on this??

 

Thanks in Advance

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (2,942)