Cloning Queries
Cloning creates a copy of an existing query. It is the quickest way to build a new query from one that already works.
When to clone
- You want a variation of an existing report (for example, the same query for a different table or filter).
- You are about to make large changes and want to keep the original intact.
- You want to use a well-tested query as a template for a new one.
What gets copied
The clone is an independent query that starts from the original's SQL and configuration. Because it is a separate query, it gets its own:
- name (you give the copy a new one),
- share hash — the clone is not shared until you enable it,
- history, starting fresh from the clone point,
- schedules — set these up anew if needed.
This separation means you can change the clone freely without any risk to the original or to anything that depends on it.
Cloning vs. drafts
- Use a draft when you want to change the same query safely.
- Use clone when you want a new, separate query based on an existing one.
After cloning, open the new query in the editor to adjust its SQL, then save.