🚀 Welcome to MDriven Learn –  Don’t miss the latest Release Notes.
Dashboards and seekers

You can use this page to find the MDriven documentation for building dashboard views and configuring seekers, whether you are presenting graph data or helping users search for records.

Dashboards

A dashboard presents summarized application information in a ViewModel. For example, a dashboard can expose the values needed by a chart, such as a performance series or a distribution shown as a pie chart.

To add Google Charts to a Turnkey application, use Documentation:Using Google Charts. The chart data must be available in the ViewModel. You can set the Angular_Ext_Component tagged value on the ViewModel columns that generate graphs, then create the corresponding components in the model assets folder.

For an example, a dashboard ViewModel can provide the data for PerformanceChart and PieChart components. Columns that supply chart data can remain in the ViewModel even when their Visible expression is false.

Seekers

A seeker is a search user interface that finds database records from criteria supplied by the user. Use a seeker when a dashboard or another view must let the user locate a record rather than display a fixed set of results.

Documentation:WECPOF Goodies describes a multi-variable seeker example where the value typed into a grid action is used as the search expression. When the search returns exactly one result, the seeker can close and assign that result; when it returns zero or many results, it stays open so the user can change the criteria.

Page seeker results

Use Documentation:Search result pages when a seeker can return more records than you want to fetch at once. The MaxFetch tagged value controls the maximum number of records returned; its default is 20 when MaxFetch is not used.

To enable paging, configure the known seeker variables described on that page.

See also