Skip to content

Report execute card

The Report execute card downloads one configured report for the current dashboard query.

When to use it

Use it for a single prominent export with no report-selection step. Use Report selector when readers need several report choices.

Live example

The Card Lab supplies deterministic report discovery data. The download action is explicitly simulated and never creates a file or contacts a backend.

Open the Report execute Card Lab in a new page

Requirements

Requirement Value
Dashboard types Standard and aggregation
Minimum size 2 columns by 2 rows
Data One report available in the current scope and the selected entity query
Backend capabilities Report listing and report execution/download
Permissions Permission to view and run the report in the current scope

Configuration

The paths below are relative to cardConfig.data.

title

Property Value
Type string
Required No
Default No title provided
Values Plain text

Sets the card heading.

entityType

Property Value
Type string
Required Yes
Default No default
Values device, interface, client, or group

Selects the current query and the report run-on value.

uniqueReportName

Property Value
Type string
Required Yes
Default No default
Values Exact report unique name

Selects one report from those available in the current scope. The action is disabled when the report list is empty.

infoAlertContent

Property Value
Type string
Required No
Default No description
Values Plain text

Adds explanatory content to the card.

Examples

Interface inventory export

{
  "cardId": "report-execute",
  "data": {
    "title": "Download interface inventory",
    "entityType": "interface",
    "uniqueReportName": "interface.inventory",
    "infoAlertContent": "The active interface search determines the report rows."
  }
}

The action downloads the configured report using the current interface query.

Behavior

The card loads reports for the current scope on initialization and selects an exact unique name. Clicking the download action uses the active entity search, or * when no context query is available. Loading and download failures are shown through notifications.

Limitations and safety

The card does not validate that the selected report’s declared entity type matches entityType before execution. Backend authorization and report validation must remain authoritative.

See Report selector.