Clockwork´s ScopeIf+ node error: "This custom node contains an invalid input. Please fix the input before saving the custom node."

Packages
1

I have an issue with Clockwork ScopeIf+ node. Its a large graph and it was working properly before.
The node now shows the warning “Warning: This custom node contains an invalid input. Please fix the input before saving the custom node.”
Rolling back Revit to a previous version isn´t an option.

Versions:
Clockwork for Dynamo 2.x
Revit 2020.1 (20.1.0.81)

Any idea from someone?

2

Change the inputs inside the custom node to look as follows

image
image.png383×532 15.3 KB

And go let @Andreas_Dieckmann know here, https://github.com/andydandy74/ClockworkForDynamo/issues

2 Likes
3

Thanks for replying @john_pierson .
The thing seems to be that way:

node_internal_error
node_internal_error.png1046×568 48.7 KB

I sent it to the Github issues link you provide.

4

Watch your capitalization. :wink:

2 Likes
5

The solution from @andydandy74:

" @AndreFernandes77 Thanks for reporting. I haven’t really started testing Clockwork in 2.1 so this might actually affect multiple nodes. I would assume you could fix this fairly easily on your end by renaming the two inputs to trueval and falseval respectively."

It works! Thanks!

6

John,
Don’t mean to hijack this thread, but the issue I had is the same and was hoping that it’s isolated. Most if not all of my scripts are based on Dynamo 2.0.2. Started using Revit 2020 with Dynamo 2.3.0 and had the same issue above with the ScopeIf+ node. The True and False inputs automatically changed to string as shown in the clip below.

image

I opened the script back up in Dynamo 2.0.2 to see what the original input values were and that lead me to the same fix as you posted above. Would you happen to know what may have caused the inputs to change on their own? I hope that this is not a prelim of issues to come.
Thanks,

7

Hi @staylor,

It looks like Andreas has fixed this is newer versions. When you update clockwork you should have the fix automatically.

The node in question:

and the line it is fixed in:

8

Hey @john_pierson
Thanks for responding, but I apologize for any misunderstanding. I actually had Clockwork version 2.3.0 installed before the issue was created, which I believe is the latest version of Clockwork.