Skip to main content
cargowise_mirror turns source evidence into current business records and explicit relationships. Use Reporting for normal reports, Power BI, exports, and reusable SQL. Use the mirror when a complex consultation needs a root, detail, or relationship that reporting does not expose.

When to use the mirror

The mirror includes consols, bookings, operational shipment details, documents, air waybill data, and other structures outside the smaller reporting contract.
Direct mirror queries must select the active generation and preserve each table’s grain and ownership rules. Internal table shapes can change as CargoWise projection support grows.

Business records

The mirror has four roots: shipments, consols, bookings, and one-off quotes. Detail tables can belong to one supported root. Bridge tables keep relationships proven by CargoWise data.

Roots

Details

Relationships

The mirror does not create a relationship from matching names, dates, routes, or amounts.

Identity and completeness

Generations

Unknown data

Unknown XML evidence remains in source_data. Scalar values can still appear through reporting.source_fields. Structured data stays in the source layer until the mirror and reporting contract support it.
The mirror reserves unmapped_fields and unmapped_items for coverage tracking. Source data remains the durable evidence for unsupported XML.
Coverage checks flag business paths and collections without an approved mirror destination. Unknown data does not become a guessed field or relationship. Next, read Reporting for the smaller model used by normal reports.