Why does the order of a collection's issues change?

Often, you'll notice that the order of the returned issues changes each time you request a collection. This is because the TBXDS does not bother with sorting the data it receives from the main database, so the final output is quite random.

Do note, that the hierarchy does not change, so you'll always be able to retrieve the data in the same way by looking at the <Ticker> values (e.g., through XPath).

For filters like "top-5", the order is important, and exactly for this reason the order attribute is added to <GroupedBy>. Note that it's theoretically impossible to have a sorted XML tree when more than one filter is used, consider: Organisation 1, 3rd on top-5, and 1st on rising-10, and Organisation 2, 1st on top-5 but 10th on rising-10. Which node should be placed first?