I want to run a report, in this case an Interactive Report over a Summary Table, and save that data to a custom table so that I can create mini-app dashboard cards with different “views” of filters/groupings on a Dashboard. users do not want to run the IR Report on the Dashboard. Should I just design my apps to pull from the Summary table, or is there a way to save off the data? What if the data is from a regular report?
For your specific question on saving report data to a custom owned table, this is a pattern in Report Builder with flat data reports which use a logic block to populate data into a report specific table and then the actual report run just reads that newly created data. This isn’t a pattern we’ve extended to application use cases though.
I need more info on why the data needs to be ‘saved’ rather than queried on the fly.
- Is there something missing from IR functionality that would make the user experience better for use on this particular dashboard?
- If you ‘could’ query summary tables from dashboard apps, would that resolve this issue?