aw_freeform_table(): sort by date if a daterange dimension is the first dimension

[gilliganondata]

It's, technically, a ranked report if the dimension is "daterangeday" and the metric is, say, "visits," but the expectation (and behavior inside AW) is that the data will be sorted by date.

Currently, the above comes back sorted by the first metric which is confusing.

[benrwoodard]

Any recommendation on how to manage this? I would hate to add another argument but assuming that 'daterange...' is always intended to be ordered by the time doesn't seem right either.

[benrwoodard]

@gilliganondata is there any reason you can think not to sort by 'daterangexxx' dimension, no matter where it is located in the list of dimensions to return?

[gilliganondata]

This makes for some tricky scenarios...but not that I can think of. A tricky scenario would be, say, Marketing Channel | Date | Visits. Analysis Workspace would sort by visits descending at the Marketing Channel first and then by Date. That feels like it would be tricky (future dev) to replicate in the current function, since you'd have to "hold" the total at the Marketing Channel level (and have the logic set up to handle that...but, maybe that wouldn't be too bad?). We definitely wouldn't want to sort by Date *first*. Sorting by Marketing Channel and then Date would be okay. Generically, though, if there is a `daterangexxx` value... it should be sorted by that. It just needs to be sorted by something else first if that's not the first dimension.

…

On Sat, Dec 5, 2020 at 3:37 PM Ben Woodard ***@***.***> wrote: @gilliganondata <https://github.com/gilliganondata> is there any reason you can think not to sort by 'daterangexxx' dimension, no matter where it is located in the list of dimensions to return? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AET7RJ73GNI7Y67DERFIEU3STKKXFANCNFSM4UJMZNGA> .