We’ve encounted an issue described below:
- If I have a dimension that I have specified an order_by clause on, I can add this to a Look and it will sort correctly.
- If I then apply a measure, say a basic count, after I’ve ran the above query, then this order_by will remain correct.
- However, if I add both the dimension & the measure at the same time and run the query, the measure will have a default descending sort applied, overriding the order_by.
Is there a way to prevent this behaviour from happening?