CaseCombResults gives back result in alphabetical order

General Discussion
1

Hello,

I don’t know if this is intended or not but the output from CaseCombResult can differ from the deconstruct components.

If I have a simple model just fort demostration. 5 bar which is modelled in the order 1 to 5:

image
image969×734 4.78 KB

Then the output from the deconstruct and CaseCombResult is in the same order:

image
image1606×775 88.6 KB

But if you change the Identifier for some of the bar (e.g. in a “real” model you maybe wanna have the identifier RR for some bars that are piles) then the lists and indexes doesn’t add up anymore:

image
image1066×761 5.26 KB

image
image1613×772 89 KB

This might be something related to when the ElementId was disconnected from the results? Where you no longer needed to recalculate your models every time you changed identifer or numbering?

2

ehi @FredrikJannesson

Thanks for raising the question. The behaviour seems to be implemented by design. I will ask anyway to the Dev team if it is necessary.

However, the safe way to manipulate results with elements is to double check that Ids are matching. As you said, you might need to do a sorting or a lookup to make sure that you are referencing the right results with the right elements.