How does iDBQuery handle different units of measure in my data?
iDBQuery reports values in the units stored in your data and, when a unit column or semantic-layer definition tells it how quantities relate, can normalise mixed units before aggregating. It shows the SQL and cites source rows, so any conversion between units like kg and tonnes stays transparent and checkable.
Operational data mixes units constantly — kilograms and tonnes, litres and gallons, hours and days, cases and eaches. Adding them together without care produces nonsense totals.
- Respects stored units. iDBQuery reads the value and any accompanying unit column and reports in that unit by default, keeping the answer faithful to the source.
- Normalisation when defined. If a unit-of-measure column exists or you record the conversion in the semantic layer, iDBQuery can convert to a common base before summing — for example rolling mixed weight units up to tonnes.
- Flags ambiguity. Where units are inconsistent or unlabelled, it surfaces that rather than guessing a conversion factor.
This is common in manufacturing, supply chain, energy, and lab data, where the same metric appears in several units across systems. Because iDBQuery cites every figure back to its exact row, you can confirm which unit each input used and how it was converted. Recording the conversion once in the semantic layer means every future answer applies it consistently, so you don't have to re-explain that a "case" is twelve units each time you ask.
Updated 2026-06-22