Whether query names in the report are buttons that emit OpenQuery.
Whether the user may turn on "skip the dry run for future query refreshes".
A refresh was applied; carries its report.
The dialog was closed.
The ID of a query the user asked to open from the report.
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.
Which queries to refresh.
Names the scope in the dialog, e.g. Query "Sales by Region" or Category "Reports".
StaticɵdirStaticɵfacReturns either the default Metadata provider or the one specified in the Provider property, if it was specified
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
Applies the refresh the dry run reported.
Turns the "skip the dry run for future query refreshes" setting on or off for this user.
The setting's checkbox changed.
Runs the dry run again, e.g. after the SQL or the database changed.
Begins a refresh: a dry run, or straight to applying when the user turned dry runs off.
<mj-query-refresh-dialog>— refreshes saved queries' metadata (fields, parameters, entities, dependencies) from their SQL and the database server, through theQuery.RefreshExtractionremote operation.Opening it always starts with a dry run: the operation reports what would change and writes nothing, live progress shows as each query is checked, and the report is shown for review. The user then applies it, which runs the refresh for real and shows what was written. When
AllowSkipDryRunis set, the review offers a user setting, "skip the dry run for future query refreshes"; with it on, a later opening applies straight away.Composite (L2): it calls the operation on
ProviderToUseand reads and writes the user setting, but never navigates: a query the user asks to open is emitted asOpenQuery.