# CaseCombResults gives back result in alphabetical order

**URL:** <https://femdesign.discourse.group/t/casecombresults-gives-back-result-in-alphabetical-order/567>\
**Category:** General Discussion\
**Created:** [5 December 2025 10:44 UTC](https://femdesign.discourse.group/t/casecombresults-gives-back-result-in-alphabetical-order/567 "2025-12-05T10:44:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![FredrikJannesson](https://avatars.discourse-cdn.com/v4/letter/f/82dd89/32.png) [@FredrikJannesson](https://femdesign.discourse.group/u/FredrikJannesson)\
**Post date:** [5 December 2025 10:44 UTC](https://femdesign.discourse.group/t/casecombresults-gives-back-result-in-alphabetical-order/567/1 "2025-12-05T10:44:55Z")

</div>

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](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/1X/3924c221817ca6753212adb3d0a846a12c84672f.png)

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

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/1X/fce65f2eb791c4058cd182a73b1d80c93a933d73.png)

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](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/1X/cac7e3c689213a9c6dc0a2b428d58b736ce71940.png)

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/1X/5d107aecdc58950040389c215cc2642880c726ca.png)

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?

---

<div class="post-metadata">

**Author:** ![MarcoPelle](https://dub1.discourse-cdn.com/flex017/user_avatar/femdesign.discourse.group/marcopelle/32/6_2.png) [@MarcoPelle](https://femdesign.discourse.group/u/MarcoPelle)\
**Post date:** [9 December 2025 08:40 UTC](https://femdesign.discourse.group/t/casecombresults-gives-back-result-in-alphabetical-order/567/2 "2025-12-09T08:40:28Z")

</div>

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.