Element.SetWorksetByName not working?

1

This seems so simple and I must assume I am missing something obvious but (per my simple script below) I can not get this node to function.

ElementsSetWorksetByName
ElementsSetWorksetByName.png1088×516 24.9 KB

To answer a few questions that might come up:

  1. Yes, the workset Columns does exist in my model.
  2. The Elements.SetWorksetByName node shows True for completeSuccess even though it is not changing the workset of the element.
2

Nevermind. I changed to workflow to the following and it works. I guess I would like to know how the Elements.SetWorksetByName actually works but it is not really important.

image
image.png1426×489 54.5 KB

3

What package was that in?

I know in recently created central models a lot of nodes act up. I fought two clockwork nodes for an hour today (detail component by curve and view) before I realized that vein in the ‘central’ I just made was messing with me. Seriously had started to close everything and was prepping for a ‘help’ post of my own. :grimacing:

1 Like
4

@jacob.small The Elements.SetWorksetByName node is from the Bakery collection.

5

I would add that “Element.SetParameterByName” must have Lacing Longest (right click, Lacing, Longest). Otherwise it changes workset for one element only.

6

@Julian_Krab Actually it was working just fine and changing all applicable elements without being set to Longest in 1.3.3. Are you working in/referring to Dynamo 2.0? What you said might be true in the new release. I will have to check when I get around to upgrading all of my graphs.

7

@rdeardorff Dynamo 1.3.3.4111
it was changing workset only for the first element from the list with Lacing Shortest (which is by default).