February 6, 2018 at 5:55pm
It is indeed possible to swap out a nested instance with a team library component.
When you use the instance dropdown on the right to swap, that list is only populated with components that are in the current document. To swap with a team library component, first drag an instance of that component into the document. Then it will show up in the instance dropdown on the ride sidebar.
We know this workflow is a tad awkward, and we're exploring options to make this interaction smoother.
Did that work for you?
February 7, 2018 at 10:22am
Hola @apuente, I don't understand your approach. Could you please explain yourself a bit more. Gracias!
Hi Jamie ( @jlfwong ) , thanks for your answer but not working really.
Your proposal implies every time a new component is added to the Team Library it must be dragged down in all the documents that is potentially needed to be swapped.
Sort of keeping a "local" Team library for each document... yeah, a tad awkward.
Anyway, I'm sure it will be fixed on next releases :)
This is a pain. Really hope they fix this. In the meantime I follow @jlfwong approach or I have to put every "swappable" instance in the same component, but hided, and then unhide the instance I want to use. :(
February 13, 2018 at 8:24pm
Hi all! Happy to announce we've just turned on a feature for everyone that should alleviate this pain. If you drag a component from the library sidebar while holding down option, instead of inserting an instance into the scene, it will swap an instance under the cursor. If you have nested components, then holding down option & command will swap the most deeply nested component under the cursor.
Please give it a try and let us know what you think!
February 14, 2018 at 8:50am
Now it's time to make it easier.
Think on an update for Team libraries, having only a search component to filter the thumbnails is poor.
Maybe a text version? Better organization? Collapsing groups? A proper item tree?
May 25, 2018 at 8:13pm
@jlfwong the OPT + CMD work around was a nice short term fix. Any chance there's a more full featured fix for swapping out a nested instance with a team library component from the instance drop down menu happening in the near term?