I'm working on a Platform Analytics Dashboard where I need to create Count Widgets with interactive filters. The challenge is that the filter values are not fields on the required table (sn_slm_case) in my case. They originate from a catalog variable captured through a Record producer. To expose this values for the reporting, I've decided to use Database View that joins the
- sn_slm_case
- question_answer (to retrieve the variable)
- cmn_cost_center (to get the required fields in this table).
This approach seems to satisfy the reporting requirement but I have concerns regarding scalability. I have come across discussions mentioning the 10,000 record limit for the Database Views with the system property (glide.db.max_view_records) but I haven't found this property in my instance, it seems to be more about the Glide Record queries but still this pops up every time I try to look out the feasibility of this approach.
If a dashboard is built on a Database view and the underlying dataset grows to 50,000+ records, will the dashboard continue to function correctly or will there be any hard platform limitations on using Database View as dashboard sources rather than building a custom field.
