Hello Dynamo people! We have changed the functionality of the “If” node in Dynamo. Previously the “If” node would work like a conditional statement, similar to the inline condition in DesignScript. So when the ‘trueValue’ and ‘falseValue’ had list values of different lengths it would replicate over…

[image] ashish.ganta: Note that this node will replicate only on the ‘test’ input parameter. I assume that means it will continue not to support list levels?

[image] ashish.ganta: Previously the “If” node would work like a conditional statement, similar to the inline condition in DesignScript. Does this mean the DesignScripts if function will not be updated with the new if node? [image] What if you have more than 1 if statement? R…

Hello @Nick_Boyts - We are happy to investigate support for List@Levels and Lacing should the need arise. With the link to the ZIP file above containing the new If Node version - would you be able to show us use cases that it doesn’t cover, which List@Level would?

@Steven the old If node used the following DesignScript code under the hood: result = test_condition ? truevalue : falsevalue; This DS conditional statement replicates over all 3 inputs, namely, test_condition, truevalue, and falsevalue. The new If node, uses the following DS code under the hood: …

Honestly I’m not sure if I have anything off the top of my head, but I feel like I’ve ran into this situation before. At least with the new node it would only take some minor list duplication to get the same outcome. I’ll see if I can put an example together.

Ok cool! We also couldn’t really figure out use cases that wouldn’t be served by this change :slight_smile: If anyone can showcase us them then great!

This is obviously a made-up use case so there are probably better ways to handle this, but this is essentially what I had in mind: a scenario where you have a list of booleans representing sublists within the true/false results. [image] Again, it wouldn’t take much to get the desired result with …

Thanks for the response @Aparajit_Pratap , [image] Aparajit_Pratap: The new If node, uses the following DS code under the hood: [truevalue, falsevalue][test_condition ? 0 : 1]; Has this style of DS always been around or is it new along with the IF node? More of a curiosity question. Thanks, …

To simply answer the question… great news :slight_smile:

[image] Steven: Has this style of DS always been around or is it new along with the IF node? This has been the DS workaround for a while. Essentially just get the sublist at the specified index rather than filter a mismatched dictionary. Completely circumvents the IF node. :+1:

[Request for Feedback] Refactored the "If" Node

Request for Feedback

Steven February 18, 2021, 6:10pm 3

Does this mean the DesignScripts if function will not be updated with the new if node?

Topic		Replies	Views
"IF" node for List Revit revit , dynamo	9	210	September 19, 2025
[Request for Feedback] If Node Request for Feedback	22	1928	February 18, 2021
If statement doesn't look good	14	180	March 10, 2024
IFnode. Can I get full list out of it? revit , dynamo	15	792	October 17, 2018
Hi guys I have some issue with node "if"	4	399	February 19, 2023

[Request for Feedback] Refactored the "If" Node

Related topics