Skip to main content
Wangwangwang
Wangwangwang
New Member
September 1, 2026
Question

Binding variation to the right collection

  • September 1, 2026
  • 1 reply
  • 26 views
  • For context, all the components needs to be binding to “Whitelabel ONLY” variable collection only. The problem is as follows…
    - clicked on parts of the component that shows binding to three different collection to investigate what other wrong binding is in the mix
    - clicked each individual parts of the components to check for incorrect binding (in this case: component common and gifted only)
    - they all show that they are binding to the correct collection, which is Whitelabel ONLY 
    - I clicked out to the parent level, only to see that it still shows the incorrect bindings! 
    - so the problem is, i dont know which part is still binded to the wrong collection?!  because on individual level, they all show the correct binding, but when clicked together, it shows incorrect binding to three different collections
     
  • PLEASE HELP, I need to handle three different component binding collections cleanly, multiplied the above situation is driving me crazy! 


     

1 reply

djv
Figmate
djv
Community Support
September 2, 2026

Hi ​@Wangwangwang, thanks for reaching out! 

I understand the frustration here and how this must be slowing down your workflow. Quick context on what you're seeing: when you select a parent, Figma aggregates every binding in the entire subtree, including bindings that don't surface when you click a single layer. That's usually why the parent and the children seem to disagree. The three most common hiding spots:

  1. Hidden layers. Toggle visibility on everything inside the component; hidden layers still count toward the parent's list.
  2. Nested instances. Expand each instance fully in the layers panel. Bindings inside a nested instance won't appear when you click the outer layer.
  3. Component properties. If a variable is bound to a component property (text content, boolean, instance swap) rather than a layer's fill or size, it lives on the main component's property definitions, not on any child layer you can click.

Also worth a quick check: is there a mode override applied at a frame level inside the component? You'd see a small mode badge next to that layer in the layers panel. A few last questions, so we can investigate further:

  • Are "Component Common" and "Gifted Only" local to this file, or coming from a subscribed library?
  • Are any of these three extended collections, or three fully separate ones?
  • Is the component you're inspecting a main component or an instance?

Let us know, and we can continue troubleshooting this together. 

Terms & ConditionsAccessibility statement