Reporting views

All client access goes through schema reporting. The login is already limited to your organization. You can also browse this contract in Lambda under Settings → Analytics → Reporting.

Views

View	Grain	Everyday use
`shipments`	One current row per Forwarding Shipment job	Main curated business table
`shipment_versions`	One row per job version	History of stored snapshots
`shipment_changes`	One row per accepted current-version change	Audit when the current version moved
`cargowise_payloads`	One row per deduplicated payload	Payload metadata and observation counts
`cargowise_deliveries`	One row per delivery event	When the delivery was received
`cargowise_messages`	One row per classified message	Message type and DataSource identity
`cargowise_xml_fields`	One row per observed semantic field	Discover field names and paths
`cargowise_xml_observations`	One row per observed field value	Query field values

Shipments columns

Column	Meaning
`job_number`	CargoWise Forwarding Shipment job number
`shipment_key`	Stable join key for versions and changes
`source_type`	Source type — rows here are Forwarding Shipment
`current_version`	Current accepted version
`current_message_id`	Current classified message id
`transport_mode`	Transport mode code
`origin_code`	Origin location code
`destination_code`	Destination location code
`total_weight`	Total weight
`total_volume`	Total volume
`goods_description`	Goods description
`first_seen_at`	First time Analytics stored the job
`last_seen_at`	Source occurrence time of the current version
`updated_at`	Database write time of the current row

Discovery columns

cargowise_xml_fields

semantic_field_key, semantic_path, label, inferred_type, total_observation_count, first_seen_at, last_seen_at

cargowise_xml_observations

semantic_field_key, payload_id, label, semantic_path, original_text, typed value columns (numeric_value, boolean_value, timestamp_value), created_at

Known curated gaps

These business concepts are not exposed as curated shipments columns today because the current Forwarding Shipment source does not supply them cleanly:

Concept	Status
Operations Rep staff code	Needs an outbound source that carries the staff code with the shipment key
Posted transaction Post Date	Needs Universal Transaction (or equivalent) posted document feed
Revenue by Post Date	Needs an agreed revenue definition plus the matching upstream feed

If those leaves exist on some other message your organization already sends, they may still appear through field discovery. They will not become friendly shipments columns until the feed and meaning are confirmed.

Access rules

Read-only SELECT statements
No writes
No cross-organization rows
No access to internal schemas behind reporting
Up to 5 concurrent sessions per credential

For connection setup see Connect. For Power BI model notes see Power BI.

Get started

Stamping

Analytics

Troubleshooting

Reporting views

Views

Shipments columns

Discovery columns

Known curated gaps

Access rules

​Views

​Shipments columns

​Discovery columns

​Known curated gaps

​Access rules

Views

Shipments columns

Discovery columns

Known curated gaps

Access rules