PlatformModel
Know what a change will touch, before you make it
The Project Map draws the whole chain on one page, from the sources to the reports and channels. It is worked out from the objects themselves, so nobody keeps it up to date by hand.
Queries
Orders by customer
Product list
Datasets
Margin by customer
Stock levels
Consumption
Sales dashboard
Delivery
Monday report
2 flows you may not see
- Reads
- 1 query
- Read by
- 1 dashboard, 1 report
Illustrative example
The whole chain, one page
Eight columns, left to right
Sources, assets, queries, flows, flow tables, datasets, consumption and delivery. One card per object, with how many objects it reads and how many read it.
Click to light up the chain
A click lights up everything upstream and downstream of a card and dims the rest. The side panel says what it reads, what reads it, its state and why.
Problems named, with a reason
Broken, warning, unused and SQL untraced are states with the reason written in the panel: a failed flow run, a deprecated dataset still read, a query nobody reads.
A save that checks first
Before a save that could break what reads it, Muvia lists what lies downstream. Nothing blocks the save: you look at the list, then choose.
How you use it
- 01
Open the map
From the Lab bar, from the command palette (Project Map), or from In the Project Map on the page of a query, a dataset, an asset, a flow or a notebook.
- 02
Select and focus
Click a card to read its chain. Use Focus to redraw only its neighbours within one to four steps, or filter by name, asset, state and kind.
- 03
Change with the list in hand
Open the object, make the change and, if something reads it, confirm after reading who. A link to the map keeps filters, selection and focus.
In detail
- Columns
- Sources, assets, queries, flows, flow tables, datasets, consumption (dashboards and notebooks), delivery (reports and channels).
- States
- Broken, warning, unused, SQL untraced. Each has its reason in the panel and none spreads downstream.
- Filters
- Name, asset, state and kind. A filter dims, it never removes. Filters, selection and focus live in the address.
- What you may not open
- Shown as one dashed card per kind, with the permission it needs: no names, and the chain does not pass through it.
- Permission
- Reading lineage needs Editor › Datasets › Read. Reports and notebooks are listed with Reports › Report › Read, flows with Post processing.
- Availability
- Part of the Lab module, which is in beta.
Frequently asked questions
No. Muvia works the chain out every time from the objects themselves, so it cannot go stale. Refresh redraws it and says when it was drawn.
No. The check before a save lists what reads the change and asks you to confirm. Deleting a query or a dataset is different: it is refused while anything reads it.
No. What you may not open is shown as a dashed card with the permission it needs, never with names. Widget and dashboard names show only with Dashboards › Read.
Bring us a question you can't answer today.
We start from a real question your business has and walk the path from source to dashboard with your systems, not a demo dataset.