So… if my recollection is right then you’re not wrong, but also not right.
This isn’t a standard node. As such the author can choose to control how it works as they see fit. So while it doesn’t work the way any of us might like or expect it to, it does work (or at least that was my recollection). The hard part is learning how we need to configure it to get the results we are after.
Here you have the sample files (Host Model and the Link Model - Revit 2024).
I also cleaned the .dyn so for testing purposes so you only need to select
the Floor Plan(s) View(s). So there is no need to change anything in the Dictionary.
The GREEN Group is for a single Floor Plan (working).
The PINK Group is for a multiple Floor Plans (not working).
I did replicate the views with a different method to match the correct structure. The method you have currently is returning an additional list level and not actually duplicating the second view.
Providing all the right inputs with the right structure and the appropriate list levels does give the output you want. There’s just a lot of extra legwork to get this to work with the intended list structures for the node inputs.
Also, you can see I used the keep list structure option for one of the inputs to keep the output structure the same - in case that’s important for anything downstream.
That’s why it’s important to confirm everything with images of exactly what you’re doing and to keep things consistent. All we have is what you show us.
Directly from the node descriptions… List.Cycle: Creates a new list by concatenating copies of a given list. List.OfRepeatedItem: Creates a list containing the given item the given number of times.
There’s really only one difference, the intended input structure. It’s probably easiest to understand just by trying them out and seeing the results for yourself.
Pretty sure i did that , i just never
noticed i screwed up my Floor Plan Cycle
until you pointed that out .
If i noticed that myself this topic wouldn’t
get ‘out of hand’ and probably solved it
myself.
Anyways, case closed.
Thanks for your help .
PS
List.Cycle also worked
(with the properLevels).
PPS
Sometimes the(se) technical terms are a bit harder to understand for not native english speaking people.
Even for native speakers they can be confusing. That’s why I always suggest playing around with them to see what happens. Both nodes can give you the exact same output you want with the right list levels, but they default to different output structures because of the expected inputs.