How does iDBQuery pick the right chart?
iDBQuery chooses a visualization from the shape of the result: a trend over time becomes a line chart, a breakdown by category a bar chart, a single number a KPI tile, and geographic data a map. You can always ask it to switch chart types or lay several onto a dashboard.
iDBQuery picks a visualization from the shape of the answer, so you usually get a sensible chart without asking: - A metric over time renders as a line chart. - A breakdown across categories renders as a bar chart. - A single value renders as a KPI tile. - Parts of a whole render as a proportional chart, and geographic results render on a map.
A worked example: ask 'monthly revenue this year' and you get a line; ask 'revenue by region' and you get bars; ask 'total revenue this quarter' and you get one big number. Ask 'where are my customers?' with location data and you get a map with pins or a choropleth.
The differentiator is that the chart follows the data, not a manual setup step; there is no dragging fields onto shelves or configuring an axis. If the default is not what you want, you just say so, 'show that as a stacked bar' or 'make it a table,' and iDBQuery re-renders. You can also compose several answers into a single live dashboard, mixing charts, tables and KPI tiles. And because every visual is backed by cited data, you can click into any bar or point to see the exact rows behind it, so the chart is auditable rather than decorative.
Updated 2026-06-22