Report Studio is a full authoring environment built into the hub. Drag fields into wells, pick a visual, add calculations, publish it to a dashboard and let people subscribe to it — over golden records, quality scores, match results, reference data and pipeline runs, on whichever engine your hub runs on. Nothing leaves the database to be analysed.
Every visual is authored the same way — fields on the left, wells in the middle, properties on the right — so learning one teaches you the rest. Switch a report's visual and the wells it needs come with it.
Charts can mix marks on one axis — plot one measure as bars and another as a line — and any chart can be split into small multiples, one panel per value of a dimension, on a shared scale.
Three panes. Drag a field into Rows, Columns, Values, Filters or Small multiples and the preview redraws as you go. Undo and redo the whole session; save with a keystroke.
One operator vocabulary across every visual. Relative dates ("last 30 days") resolve as the reader opens the report. A filter can be required, a parameter, or carry a default — and the reader sees which.
A filter on a field with few enough distinct values becomes a picker automatically — the threshold is one central setting, adjustable per person or per model. Values are read through the same governed door as the data, so masking and row-level rules still apply.
Write an expression once and use it like any other field. Expressions are compiled to SQL for the hub engine you are on — nothing an author typed is ever sent to the database as text.
Sum, average, count, distinct count, min and max — with ordering, Top N and an "Other" bucket, having-clauses, and show-as windows: % of total, % of a grouping, running totals and rank. Group a date by day, week, month, quarter or year without adding a column — the truncation is computed by whichever hub engine you are on, and the report echoes the grain it actually applied, because a silently ignored grain mislabels an axis.
One rule set per column, drawn five ways: an indicator, a heat bar, a badge, a range against a target, or a delta against another column. Change a threshold and every mark on that column moves together — a bar and a badge on one column cannot disagree, because there is only one place the answer lives. The same marks reach matrix and pivot measures, and row and column headers.
Thresholds and bands for numbers; contains, starts with, is one of and wildcards for text; on, before and in the last 30 days for dates, resolved as the reader opens the report. A value can name another column, so every domain is judged against its own target rather than one global number. A blank cell matches only is blank — an unmeasured score is never painted as a zero.
Colour scales, icons and value rules on table columns, and banded gauge and bullet cards that paint in the direction being scored — so lower-is-better reads correctly. The band editor warns about gaps and overlaps, and can suggest bands from the data's own distribution — with the AI narrating the choice, and the arithmetic deciding it.
The report picker opens with a Recent list — the few reports you actually work in, ranked by how often and how recently you opened them, each showing when you last had it open. It is kept per person and resolved against the reports the server says you may open, so one that was deleted or is no longer yours simply is not on it. The property panes fold as well, and remember what you folded — each closed group states what it is hiding, and a well opens itself the moment you drag a field toward it.
Dashboards in MDM Studio are a canvas, not a fixed grid. Tiles reflow, fit, fill or lock their aspect; the canvas takes a colour, image, pattern or grid; and titles are formatted like text, not like settings.
customer_id here is cust_id there. Pick the field on each source by hand instead. Suggestions are offered with their evidence — same key, same type, 80% shared values — but nothing is ever bound without you confirming it.Any set of filters, sorts and drill positions can be saved as a named view, made the default, or shared with the report — so "the version I actually look at" is a link, not a ritual.
Schedule a report or a whole dashboard to arrive by email. Each run executes as the subscriber, so nobody is ever mailed rows they could not open themselves — and when no mail server is configured the run is recorded as skipped, not as sent.
CSV and Excel are generated on the server against the same governed query the screen ran — so an export is the report, not a re-derivation of it. Print keeps the layout.
Subscribe to a job, a job group or an execution package and hear about starts, successes and failures in-app or by email. One incident sends one letter — the most specific scope wins, so watching a job and its group does not double up.
Click into a bar, a cell or a KPI card and the report walks the ladder you defined — down a level, up again, or straight to first or last. The pivot follows the same ladder as the chart.
Reports read through the product's own access layer. Sensitivity clearance, row-level access groups and tenant isolation apply to a report exactly as they apply to the record screen, and filter and sort keys are allow-listed against the source catalog.
Most reporting tools will draw something no matter what you feed them. A picture of the wrong thing is worse than no picture, because nobody checks it. MDM Studio refuses instead, and names the reason on the visual.
A display format is governed once on the attribute, in the data dictionary, and every surface honours it — grids, chart data labels, axis ticks, KPI cards and exports.
Report Studio reads the product's own governed sources — no warehouse hop, no nightly extract, no second copy to secure. The dashboard's own domain-health and severity queries are published here as sources, carrying the same access scoping they have on the dashboard — so a narrowed steward never sees their slice of records beside a whole domain's exception count.
A report answers a question you already knew to ask. The Explorer is for the other kind — somebody hands you a key and asks whose it is. Start on an entity, walk its relationships tab by tab, and make any related row the new focus with a breadcrumb trail behind you.
The fastest way to judge a reporting layer is to point it at a real question. Bring one, and we will build the report with you in the session.