While dashboards are great for their interactive content, there are executives that would rather see a static presentation of the dashboard at a point-in-time that they can reference, carry around, post on intranet sites, etc. If we could run a dashboard through CLI/API and save the output, using field filtering to set any required project filters, and a parameter to save the output to (similar to "im runreport...") we could have a static view of a dashboard that exactly matches the format that people are used to running interactively.
This speaks to a comment in another product idea about being able to run a dashboard ahead of time, given that they can take a long time to run. If a static view is all that's needed, the approach of running the dashboard, saving the output to a file, and publishing it would solve this long-running dashboard need as well.
With this static presentation concept in place, I would then look to have the --asOf parameter added and passed to all of the embedded dashboard components (reports, charts, etc) so that the entire dashboard can be rendered at a point in time and saved.