fabric-realtime-dashboardlisted

Use for Microsoft Fabric Real-Time Dashboards (KQLDashboard item) — authoring or editing RealTimeDashboard.json by hand or via Git: file anatomy (queries[] holds all KQL text; tiles reference it by queryRef.queryId; baseQueries are {id, variableName, queryId} wired through usedVariables), load-time validation (every queryId referenced exactly once, RFC-4122 UUIDs, identity preservation — changing ids = delete+recreate on sync, misleading 'baseQueryId' error = malformed queryId), the 24-column tile grid, visual types (card, multistat, bar, column, table, map, kpi) and visualOptions, the kpi gauge's static-only min/max/reference lines, autoRefresh intervals, display-edge formatting in KQL (no per-tile number formats — emit currency/percent as strings), the live JSON Schema at dataexplorer.azure.com/static/d/schema/{v}/dashboard.json, and the missing image-export REST API. Invoke on mentions of Real-Time Dashboard, RTDB, KQL dashboard, dashboard tiles/base queries, or RealTimeDashboard.json.
wardawgmalvicious/agent-config · ★ 0 · API & Backend · score 75

Install: claude install-skill wardawgmalvicious/agent-config

# Fabric Real-Time Dashboard (KQLDashboard) Hand-authoring and Git-editing the `RealTimeDashboard.json` definition. The portal load endpoint validates beyond JSON Schema conformance — most of what breaks a hand-authored dashboard is in the wiring rules below, not the syntax. Facts verified against a live dashboard (schema_version 81, Aug 2026) and [Real-time dashboard - Git integration](https://learn.microsoft.com/fabric/real-time-intelligence/git-real-time-dashboard). ## File anatomy Item folder: `<Name>.KQLDashboard/` with `.platform` + `RealTimeDashboard.json` (portal may name it `RealTimeDashboard-N.json`). Top-level keys: `schema_version`, `flavor` (`"RTDashboard_Regular"`), `autoRefresh`, `tiles`, `baseQueries`, `parameters`, `dataSources`, `pages`, `queries`, `embeddedApps` (+ portal-managed `$schema`/`id`/`eTag`/`title`, which a Git-created shell may omit — leave them however the portal wrote them). All KQL text lives in `queries[]`; everything else points at it: - `queries[]` — `{id, dataSource: {kind: "inline", dataSourceId}, text, usedVariables}` - `tiles[]` — `{id, queryRef: {kind: "query", queryId} | {kind: "baseQuery", baseQueryId}, title, visualType, pageId, layout, visualOptions}` - `baseQueries[]` — `{id, variableName, queryId}`; the text is the referenced query object. Variable names must start with `_`. A tile query that uses one references the variable in its KQL text **and** lists it in `usedVariables`. Base queries must each be a single tabula