In our implementation, we are sourcing a few personalized tables with paginated data pages (which are in turn sourced by reports) due to the volume of data received. We have noticed that whenever a paginated data page is ran, it applies an ORDER BY clause to the generated SQL which overrides any ordering or sorting applied to sourcing report definition; specifically "ORDER BY 1 ASC, 2 ASC, 3 ASC...". This makes it difficult to show the proper data to the user on screen load. Is this in the works as an enhancement? Or is there a work-around we are unaware of?