Can't connect component properties in collection

Hey everyone!

I followed the tutorial on how to create component properties and connect them to collection data but… I don’t have the purple + showing in the properties panel of the instance.

Am I missing something obvious?

Thanks in advance!

The component with its properties

One instance (I can’t link properties to the collection data)

First of all right click the image from your mouse then select with your collection image field

Thanks for your help but it appears there’s nothing else there (or am I missing something?):

Could be a glitch, but just in case- is the collection list actually bound to a collection?

I thought that the collection had to be in the component

I wish it wasn’t :sweat_smile:
But it is :point_down:

You can share your readonly project link, and I can have a look however some parts of the designer UX are not accessible in readonly view, so I’m not sure I’ll see the same thing.

I’m facing exactly the same issue. Were you able to figure it out and are happy to share?

Also having this issue!

For anyone wondering I just did a little test and this is only true for CMS collections for Ecommerce related items

Wondering if anyone managed to bind a component to a Product collection at all? Is this really not possible?

Hey @Dan_C,

I reached out to Webflow and this was their response:

Unfortunately, you will not be able to use Components inside of Ecommerce-bound Collection lists.

At the moment, we are aware of the limitation that users are unable to bind Ecommerce fields to Component properties. While Ecommerce products function the same as CMS collections, there is a lot of underlying complexity in the way we handle bindings for Ecommerce data that differs from normal collections. This prevents us from binding them to Component Properties.

The only workaround at the moment would be to not use Components inside of Ecommerce-bound Collection lists (unless they don’t require bindings to dynamic fields).

I wish I could deliver better news on this but this is a limitation we have at this time. I’ll be sure to relay this to our product teams internally and advocate for this as I can certainly understand how it would be useful for you in this case.

Thanks for that. At least we know :slight_smile: