Status, naming and governance

The query list carries Query title, KPI Name, KPI Id, Creator, Created, Updated and Status (Active, Draft, or Archived — 10.3 covers what archiving actually does), with a status filter and a search box above it, and two actions per row — delete and duplicate. It's entirely normal to see the same KPI Name more than once in this list — every row still carries its own unique KPI Id, which is what actually identifies it, so a shared name is never ambiguous in practice.

The duplicate icon copies a query in one click, no confirmation needed: it creates a new row titled "<original title> (1)", on Draft, with Assigned KPI cleared back to "Please select a KPI" — but the canvas itself, every component and operator in the formula, carries over exactly as it was. This is the fast way to start a new KPI from an existing formula as a template, without touching the original: duplicate it, then assign the new KPI and adjust the calculation from there.

The delete icon does confirm — a "Query deletion" dialog asks "Are you sure you want to delete this query?" with Cancel and Delete buttons, so there's no accidental one-click loss.

⭐ The real lesson isn't the mechanics of building a KPI — those are three lessons of straightforward form-filling. It's that a custom KPI propagates everywhere: dashboards, planning, driver trees, investor reports. Unlike a standard KPI, it can also be edited and deleted. That combination — wide reach, loose control — is exactly why the question worth asking before every new KPI is not "can I build this" but "should I, or does one already exist."