Skip to main content

I’m trying to create a Boolean Property on my “Icon” layer inside a button Component, but when I click on the Icon layer, the Layer section in the RIGHT PANEL does not show up. (see screenshot). To be clear, I’m not talking about the left Layers panel. I mean the Layer: Passthrough section in the right panel.


When I even just create a basic shape (not a component) in my frame, I still don’t see the Layer section in the RIGHT PANEL, why??


I’m also looking for the ability to create a ‘boolean property’, but with the new UI, the button seems to have disappeared. Has this feature been renamed or moved somewhere else?




Edit:


Oh, never mind, I found it.





Edit 2:


Actually… I can’t find where to apply the boolean property to a layer. So I’m still stuck.



Layer panel is Appearance now. So the boolean property is here



@andreaszzz - You may be trying to add a property on an element within an instance of a component, instead of the component itself. In that case you won’t see the boolean property button on the layer/appearance (and you also shouldn’t have before the updated Figma UI).


I’m sure you might have already got to this, but I also was having a similar problem.


I figured out that for some files the boolean icon appears and in others it doesn’t (maybe something to do with the age or permissions of a file?) but I found that when the button wasn’t in the right appearance panel, it shows up as a different icon, where you can choose either a variable or a property option



Clicking on this lets you select from either the root component, or from other libraries.


This is what I was looking for. I must say the constant changes that keep coming from Figma are not always easy to keep up with especially for someone fairly new to it. Thank you for posting this!




I have the same Issues only swap instance is showing


I have the same issues


You saved me, thank you! 🤩


So weird that in the same file one component has it outside and another one in a second level like this.


Non-issue, but just commenting that I was also thrown off by this change for a couple of minutes before looking up this thread. (The new way works, it’s just not as intuitive)


God saved my life - thanks for posting, it’s so hidden!


Thank you guys you made my day for this solution given


Thanks! Old UX for this was way faster and more intuitive when building components. Why change to this?


Reply