Whether to auto-run the query when all required params have saved values
Fired when a composition token ({{query:"..."}}) is clicked in the SQL info panel
Fired when an entity link is clicked in the grid
The parameter values the rows on screen were produced with (mapped ones included, server-set ones left out), or null before the first successful run. The grid's Open in Excel carries them.
Fired when user wants to open the full query record
Number of rows per page for server-side paging. Set to 0 to disable paging and load all rows at once.
What the parameter form shows: the user's values, with the mapped ones over them.
Whether to persist parameter values
Whether to persist grid state
If specified, this provider will be used for communication and for all metadata purposes. By default, if not provided, the Metadata and RunView classes are used for this and the default GraphQLDataProvider is used which is connected to the same back-end MJAPI instance as the Metadata and RunView classes. If you want to have this component connect to a different MJAPI back-end, create an instance of a ProviderBase sub-class like GraphQLDataProvider/etc, and configure it as appropriate to connect to the MJAPI back-end you want to use, and then pass it in here.
Fired when query execution completes
Fired when query execution fails
Fired when query execution starts
Paging state
The names of the mapped parameters, which the parameter form shows read-only.
Fired when a row is double-clicked
Fired when selection changes
Selection mode for the grid
Whether to show the toolbar
Visual configuration for the grid
StaticɵdirStaticɵfacParameter values the host sets (a dashboard part's input mappings). They override the user's
saved values, are never saved back into the user's last-used set (QueryViewer_<id>_LastParams,
which every page showing the query shares), and show read-only in the parameter form. A change
reruns a query that has run; before the first run, the query's own load uses them. Null (the
default): every parameter is the user's, as before.
Returns either the default Metadata provider or the one specified in the Provider property, if it was specified
The ID of the query to display
Returns either the default RunQuery provider or the one specified in the Provider property, if it was specified
Returns either the default RunView provider or the one specified in the Provider property, if it was specified
The user's own parameter values: loaded from and saved to their last-used set. Never holds a mapped value it didn't have.
Fetches the FULL result set for the current query, used by the grid's export flow so exports
aren't capped at the on-screen page (bug B3). Bound as an arrow property so it can be passed to
the grid's ExportDataProvider input without losing this. Loads up to EXPORT_MAX_RECORDS
(kept in lockstep with the entity-viewer's export cap) and warns — rather than silently
truncating — when the query returns more. Uses the provider-scoped RunQuery so it targets the
correct server in multi-provider setups. Falls back to the currently-loaded page on failure.
A callback method that performs custom clean-up, invoked immediately before a directive, pipe, or service instance is destroyed.
A callback method that is invoked immediately after the default change detector has checked the directive's data-bound properties for the first time, and before any of the view or content children have been checked. It is invoked only once when the directive is instantiated.
A composite component that provides a complete query viewing experience. Features:
Example