Skip to main content
Curated views are the least-friction path. Use them for dashboards, recurring reports, and anyone who is not hunting through discovery fields.

Start with shipments

reporting.shipments is one current row per Forwarding Shipment job for your organization. Useful columns:
  • job_number — the CargoWise job number people recognize in operations
  • shipment_key — join key for history tables
  • transport_mode, origin_code, destination_code
  • total_weight, total_volume, goods_description
  • first_seen_at, last_seen_at, updated_at
Join history with shipment_key:

Browse the contract in Lambda

Open Settings → Analytics and expand Reporting. That section lists the supported views and columns for your organization. The same list is documented in Reporting views.

When curated data is not enough

If the column you need is not on shipments, do not assume the value is missing from Analytics.
  1. Search Discover fields.
  2. If the field is present in observations and becomes a permanent report need, ask Jaantonio to evaluate promoting it into a curated table.
  3. Some business concepts need a different upstream feed before they can appear as curated columns. Operations Rep, Post Date, and Revenue are examples of that today.

Practical guidance

Prefer job_number in business-facing filters and exports. Keep shipment_key for joins. Use curated tables for Power BI overview pages. Leave discovery observations for field hunting and detail work, not for every visual on a busy dashboard.