Hi,
Wanted to understand on how Appian parses an Expression Rule that uses a!queryAggregation and a!queryAggregationColumn against a Table/View? Does it convert and send a query as-is with GROUP By to the database SQL engine or does it get the data and then do the grouping on-fly in its memory?
Thank you in advance for your response.
Discussion posts and replies are publicly visible
It's intentionally obfuscated through the Appian-based abstraction layer (the data store, at least for the older data types), particularly so that they can shift things around in the back-end on a progressive basis to tweak efficiency without breaking the way things work on the Designer front-end. That's all a long way of saying, we don't "officially" have any way of directly knowing what the exact SQL is that eventually gets passed to the DB via the Appian query, but it's reasonably safe to assume that by now they've probably fine-tuned it to be reasonably close to the most efficient thing possible.