Present State: when you’re using aggregate models, you need to manually remove model limits and ordering, since these don’t work with aggregations (and cause the page to bomb, with a helpful error statement).
It would be great if Skuid could do more of the thinking/configuring for users here: When a model is marked aggregate, Skuid should automatically remove model limits and ordering (or even have these fields not render in the properties panel, since using them causes problems).
I agree that often these properties can be problematic, but technically there is a place for both limits and ordering with Aggregates — we should improve our “Order By” property to prevent users from ordering on fields that will cause the Model’s query to fail, and recommend not to use limits in certain scenarios.
