Custom nodes in Dynamo 2.2

[wma_sfenton]

Since the Dynamo 2.2 update a one of our custom nodes will not work, can anyone explain what has changed so I can repair our nodes and scripts?!

[Alban_de_Chasteigner]

Hi @wma_sfenton,

The spaces in the names of inputs and reserved keywords are no longer supported in latest Dynamo 2.X versions.

Replace the inputs with :
view/Elements:var[]..[]
and :
titleBlockType:var[]..[]

2.2 Data-Shape UI.Dropdown Data Node

I think in later versions of Dynamo we stopped supporting spaces in the names of inputs for customNodes - this is to match the syntax for a valid ID in designscript and to fix a bug where these names were getting modified when the node was saved - but the node should still run, and unless you’re editing this custom node shouldn’t need to be saved.

[Arno_De_Lange]

But why does this give an error, TExtNote is a reserved text by the looks of it, but when i change it to TextN… it stays red

[vanman]

What would i change this too? I’m worried I get something wrong.

[Michael_Kirschner2]

the error shows an example of a valid input string - you have two types (string and var[]..[]) and two : this is not valid.

[Michael_Kirschner2]

I don’t think [ and ] are valid name characters - try sticking to alphanumeric strings for names starting with a letter.

I would also advise not using type names exactly as names - so List and Type are bad names as these might collide with valid types.

[vanman]

Will the script work the same no matter whats in “Input”, as long as it dosn’t have spaces and special characters? So I dont need “Type” at all for any reason but for user understanding? “TitleBlock” by its self will not change the functionality of the script?

Letters changing color makes me think there is some functionality going on with the input I need. My limited understanding