What is the current behavior?
Currently, when the o-tree component is not pageable, child nodes are not sorted in a predictable manner. This can lead to confusion in the hierarchical view, especially when users expect an alphabetical or predefined order.
Steps to reproduce
<o-tree #treeview fxFlex root-title="CUSTOMERS" service="customers" entity="customer" keys="CUSTOMERID" ...>
<o-tree-node service="customers" entity="customerAccount" quick-filter-columns="ACCOUNT" columns="ACCOUNTID;CUSTOMERID;ACCOUNT;STARTDATE"
sort-column="STARTDATE:desc" visible-columns="ACCOUNT" keys="ACCOUNTID" parent-keys="CUSTOMERID">
......
The account nodes are not sorted
Affected versions:
What is the current behavior?
Currently, when the o-tree component is not pageable, child nodes are not sorted in a predictable manner. This can lead to confusion in the hierarchical view, especially when users expect an alphabetical or predefined order.
Steps to reproduce
The account nodes are not sorted
Affected versions:
ontimize-web-ngx: 15.x.x