Build a dashboard from a picture
Esta página aún no está disponible en español. Se muestra la versión en inglés.
Send Querri a picture of a dashboard, from any tool or a slide, and it rebuilds what it can see as a Querri dashboard: the same widgets, in the same places, in colors it reads off the image. Then it puts data behind them, either generated to match the numbers in the picture or read from your own sources.
Who can see this: anyone signed in. An API key can’t start one, and none of this appears in an embed. Anyone who can open the dashboard can watch it being built; only the person who started a build can stop it.
How you start it
Section titled “How you start it”Paste, drop or attach a picture of a dashboard in the chat panel, send it with any wording, and the rebuild begins. There’s no separate button: the picture is the request. Start from a screenshot, on the panel that opens from New Dashboard, is a shortcut to the same thing. It opens the file picker and the picture goes with your next message. An empty chat panel says you can do this too.
Where you start decides what you get. From Dashboards, or anywhere else in the app, you get a dashboard. From Projects you get a project instead, and no dashboard is made. See A picture rebuilt as a project.
What happens
Section titled “What happens”- It reads the picture. The chat says it’s reading the screenshot, then how many widgets it read values from, then how many elements it found. This takes about a minute.
- It shows a plan. A Replication plan card, with the dashboard’s name, a thumbnail of your picture, a line counting what it matched, approximated, couldn’t read and can’t do yet, the colors it picked, and three lists you can open: Approximated, Not read and Not possible yet. Open dashboard opens what it built. If the picture isn’t a dashboard it says what it looks like instead and offers Build it anyway.
- It may ask where the data comes from. Only when you didn’t say and your organization has sources connected. The two answers are Generate mock data in a new project and Use data I’ve already connected.
- You approve the build. A card above the composer names what it will build, such as Put mock data behind “Q3 Revenue” or Build “Q3 Revenue” with your data, and says the layout stays as it is and the project can be deleted at any time. The buttons are Build with mock data or Build with my data, and Not now. Nothing is built until you press one.
- If you chose your own data, you match the widgets to it. A card lists every widget with Use my data or Mock this one. A matched row asks for a source, a date or category column, an aggregate such as sum or average, and the number to measure, one per series. A row that isn’t ready says what’s missing, the footer counts them, and a link mocks the ones you haven’t matched. Build starts when nothing is outstanding.
- It builds. A panel names the phase it’s on with a counter: building the data, adding it to your Library, creating the project, running the steps, binding the dashboard. It runs in the background, so you can keep chatting, and Cancel stops it after the step it’s on.
- Replication plan: what it read, and what it built from it.
- The thumbnail: the picture you sent.
- The counts: matched, approximated, not read, not possible yet.
- Approximated: what it drew differently, and why.
- Open dashboard: open what it built.
Mock data and your data
Section titled “Mock data and your data”A widget is built on mock data whenever the build carries no match for it, or the match doesn’t hold: a chart with more than one series only reads your data when every series has a number column, and a source you can no longer read falls back to mock data as it builds. Mock data is generated to reproduce the numbers read from the picture, and it’s saved in your Library like any other source. None of it is real.
Use my own data, on the dashboard’s banner, switches a finished mock replica over. It’s offered once: after that the button is gone, and asking again is refused with a note telling you to paste the picture again for a fresh one. A project built from a picture can’t be switched at all.
If the switch doesn’t work, the dashboard is handed back to its mock build untouched. The banner says so, nothing on the dashboard changed, and the button stays for another try.
When some elements couldn’t be built, the banner adds a sentence counting them and saying they still show mock data, or still show the numbers read from the picture.
When nothing on the dashboard reads data at all, because every element is a card, a table or text holding what was read, it says so and stops before offering to build anything.
The banner
Section titled “The banner”A dashboard built from a picture carries a banner at the top: a thumbnail of the original, the label Replica of your screenshot, a line about where it’s up to, and an X to dismiss it. It’s never shown in an embed.
| Where it’s up to | What the banner tells you |
|---|---|
| Read, nothing built yet | The numbers shown were read from the screenshot, and you can ask in chat to build mock data behind them |
| Nothing on it reads data | The numbers were read from the screenshot, and it’s finished as it is |
| Building | Which phase it’s on, that your edits are kept, and that the widgets switch over when it finishes |
| Built, waiting for you to reload | The data is built, and the widgets show the numbers read from the screenshot until you reload |
| Switching over by itself | The data is built and the widgets are switching over |
| Finished on mock data | How many elements read from project steps, and that nothing on it is real yet |
| Finished on your data | How many elements read your sources |
| Finished on both | How many read your data, and how many use mock data |
| It failed | Why, and that the numbers shown are still the ones read from the screenshot |
Its buttons are Use my own data, Check against screenshot, and Reload to see it when the page is holding a finished build back from the canvas.
- The thumbnail: the picture this was built from. Click it to see the original.
- Replica of your screenshot: how this dashboard was made.
- The state line: what the widgets are reading.
- Use my own data: move it off mock data, once.
- Check against screenshot: compare it with the original and fix what differs.
A build that finishes while you’re looking
Section titled “A build that finishes while you’re looking”The widgets switch over on their own, with no reload. The one exception is a dashboard you’re editing, or one with unsaved changes: the canvas is never swapped out from under you, so the banner says the widgets still show the numbers read from the picture and offers Reload to see it.
If you reload in the middle of a build, the banner and the chat both pick the build up again. Pressing an old approval a second time doesn’t rebuild anything; it says what already happened.
Check against screenshot
Section titled “Check against screenshot”Check against screenshot asks the assistant to compare the dashboard with the picture it was rebuilt from and fix what differs. It changes styling, chart settings and sizes only. The data and a chart’s type are left alone, because the numbers are meant to differ. It needs the dashboard in edit mode, and it can run twice per replica.
What it says it couldn’t do
Section titled “What it says it couldn’t do”The plan card and the banner both name what didn’t make it, one line per element:
- Not read: a chart, table, card or title it couldn’t make out. On the canvas an unread widget becomes a muted note saying so.
- Approximated: drawn, but differently. Filters arrive as labels until the data is built, and a row that can’t fit at a readable width is split across two.
- Not possible yet: things a Querri dashboard doesn’t have, such as a report download button, or the original page’s own navigation, since a Querri dashboard is one page.
Limits
Section titled “Limits”One picture at a time per person, and five per organization each hour. Reading stops after 8 minutes and a build after 30.
A picture rebuilt as a project
Section titled “A picture rebuilt as a project”Send the picture from Projects and its charts and tables are rebuilt as project steps instead. The project is created when you approve, and you land in it with the Data Flow pane open, watching the steps arrive. Generated data becomes a source in your Library. A strip in the Data Flow toolbar shows the phase and a Stop rebuild button, and steps that finished before you stop it are kept. When the build lands, the project’s chat gets a summary with a card for each element it rebuilt.
Credits
Section titled “Credits”Rebuilding costs nothing in itself. The chat turns that start it and report on it are charged as ordinary questions: a message in the chat panel is one question to the Librarian, 1 credit. See Credits.