Remove limits and ordering when a model is marked aggregate

  • 2
  • Idea
  • Updated 3 years ago
  • Under Consideration
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).
Photo of Anna Wiersema

Anna Wiersema

  • 10,890 Points 10k badge 2x thumb

Posted 3 years ago

  • 2
Photo of Zach McElrath

Zach McElrath, Employee

  • 49,004 Points 20k badge 2x thumb
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.