Find your containers on the Container Dashboard

The System Views and what each one means

The System Views button sits at the left of the tab rail. Open it and you get eight platform views, each with its live row count in parentheses and its fixed criteria as the hover title. These are the exact criteria strings the app shows:

All Active

Status = All Active - Tracking sync = Active tracking. Every status, active lifecycle only.

Abandoned Work

Lifecycle = Abandoned. The only view that shows non-active rows, and it shows delivery-order rows only.

On Water

Status = On Water - All sync states.

At Terminal

Status = At Terminal/Scheduled - All sync states. Two statuses, which is why Status stays as a column.

At Risk

Status = At Terminal/Scheduled - LFD through tomorrow - All sync states.

At Risk Return

Status = Gate Out - LMTFD through tomorrow - All sync states.

Gate Out Today

Movement = Gate Out - Gate Out date = Today - All sync states.

Gate In Today

Movement = Gate In - Gate In date = Today - All sync states.

Picking one writes systemView=<id> into the URL and clears any explicit filter parameters, so the view you see is the view the criteria describe. Each System View also carries its own curated column set — On Water leads with Vessel and ETA, Gate Out Today leads with Delivery Location and driver, At Risk Return leads with Return Terminal and the empty deadline. While a System View is active, a Save as custom view button appears next to it in the popover; that copies the whole state into a saved tab you own.

Two behaviors the criteria line does not tell you

At Risk pulls in extra rows. On top of the status and date gates, it joins in containers carrying a termination risk, hot loads that are not yet delivered or returned, and rows with a review risk. Those rows bypass the status and date gates only — search, owner, source, and sync filters still apply to them. So At Risk can legitimately list a container whose LFD is not through tomorrow.

Every other view hides abandoned work. Rows whose lifecycle is not active are filtered out of all views except Abandoned Work. If a delivery order vanished from your tab and you know it exists, check Abandoned Work before you report it missing.

Where you land on first visit — the priority chain and the seeded tabs

The server resolves your landing view in a fixed order and stops at the first thing that claims it:

1. The watchlist. watchlist=1 or savedOnly=1 in the URL opens My Watchlist and ignores everything below.
2. A named System View. A recognized systemView id opens that view with its curated columns.
3. Explicit filters in the URL. Any of statuses, sourceKinds, ownerOrgIds, trackingSyncStates, dateField, dateRangePreset, customDateStart, customDateEnd, daysOldMin, daysOldMax, dateStart, dateEnd, or search lands you on an unsaved Custom view.
4. A named saved view. A view parameter that resolves to one of your saved views opens it.
5. Your default saved view. Otherwise the view you marked default, or the first tab in your order.
6. The fallback tab. If nothing above claimed the landing, you get the built-in On Water / At Terminal state.

The two seeded tabs

If you have no saved views at all for this workspace, the dashboard creates two for you on that first load: On Water / At Terminal, marked as your default, and Gate Out / Gate In. Both ship with a working column layout — Broker Ref, Vessel, ETA, and SSL ETA promoted behind Container — and sort by ETA, newest first.

They are ordinary personal saved views from that moment on: rename them, reorder them by dragging the tab, update them in place, change which one is default, or delete them. Deleting every view is allowed; the pair comes back the next time you open the dashboard with none saved.

Filtering, including per-column filters

There are three separate filter layers, and they do not do the same job. Knowing which one you are in explains most “my rows disappeared” moments.

1. Report settings — what the view loads

Click the view name in the toolbar (it carries a gear and a chevron) to open the Report settings panel. The Filters row is a collapsed one-line summary; when nothing is set it reads like “No filters · full 120d history · 4,231 rows” where the day count is your workspace history window. Expand it for:

1. Date — pick a date field (the placeholder is “Select a date field”; No date field clears it) and then a range. Set a range with no field and the heading changes to Date — field required and the gear turns amber.
2. Status — a multi-select summarized as All statuses. At least one status must stay selected.
3. Criteria — Tracking Sync (All sync states: Active tracking, Paused conflict, Tracking complete) in every workspace. Forwarder and warehouse workspaces also get Source (All sources: Native D/O, Managed Tracking) and Owner (All owners). Carrier workspaces do not show Source or Owner.

Reset filters at the bottom of the panel returns the view definition to its baseline.

2. Search — one box, scoped to the active view

The search box carries the view name in its placeholder (“Search On Water,” and so on) so you always know what you are narrowing. Focus it and a hint panel explains the grammar: it matches any column and terms combine to narrow (msc newark hold); status and flag words such as on water, at terminal, available, gate out, gate in, hold, and hot load are understood; and dates take forms like lfd today, eta before YYYY-MM-DD, and lfd between YYYY-MM-DD and YYYY-MM-DD.

A query the planner cannot parse turns the box amber and shows the validation error in that same panel instead of silently emptying the grid. When a search is active, a Search all history link appears beside the history chip and hands the same query to workspace search, which is not bounded by the dashboard's history window.

3. Per-column filters — the funnel in each header

Every column header carries a small funnel button. Its accessible name reports the column's state — Sorted, Filtered, or Sorted + Filtered — and the button turns blue when either is on. The popover header repeats the column name and, immediately below it, the caption Loaded rows only. Take that literally: column filters run against the rows already in your browser, not against the database.

1. Sorting. Text columns offer Sort A to Z and Sort Z to A; date columns offer Sort oldest to newest and Sort newest to oldest. Clear sort is disabled until a sort exists.
2. Filter by condition on a text column: Contains (with a Text box), Is blank, Is not blank.
3. Filter by condition on a date column: Is, Before, After, Between (Start and End), Is blank, Is not blank.
4. Filter by values on columns like Status, Holds, Carrier, or Pickup Terminal: a checklist with a per-value row count, Select all and Clear, and a search box. Only 200 values render at once — past that the list tells you to refine the search to narrow the remainder.

Changes are a draft until you press OK; Cancel throws them away, and Clear filter empties the draft. Once any column filter or search is on, the row count in the toolbar switches from a plain total to “visible of loaded” — for example “128 of 4,231 rows”.

Showing, hiding, and reordering columns

Column control lives in the same Report settings panel, in the Columns section below the filters.

1. Container is pinned. It renders as row 01 with a disabled checkbox and the marker Always shown. It always sorts to the front of the column order, and a stored attempt to hide it is discarded on load.
2. Show or hide. Tick or untick any other column. The list is numbered from 02 down, in the order the grid will render.
3. Reorder. Drag a row to move it, or move it with the keyboard from the row's own controls. Dragging starts after a short pointer movement, so a plain click still toggles the checkbox.
4. Start over. Reset columns/order restores your workspace defaults. It is disabled when nothing has changed.

Column changes are part of the view state, so they follow whatever tab you are on. On a saved tab, update the tab to keep them; on a System View, use Save as custom view. The “columns changed” indicator compares against the active view's own baseline, not the stock defaults — so a curated System View does not read as customized just because it differs from the plain default set.

Reading it on a phone

Below the desktop breakpoint the table is replaced entirely by a card list. There is no horizontal scrolling and no column grid; each container is one tappable card that opens its detail page.

What each card shows

Container number in monospace with a reference line under it, a status pill, a Holds line (an em dash when there are none), the counterparty name with a Termination chip when it applies, a route line of pickup terminal → return terminal · vessel (or “Route pending”), and the next relevant date with its label.

How much loads

24 cards to start. A “Show 24 more” button at the bottom adds another batch and reports how many of the total you are looking at.

The tab rail collapses into a single View dropdown listing the eight System Views with their counts, then My Watchlist, then your saved views. If you arrived on an unsaved custom state, it appears as a greyed-out Custom view entry you cannot re-select.

Limits — the row budget and the history window

The dashboard does not page through the server on every click. It downloads one working set and does all view switching, sorting, searching, and column filtering locally. Two numbers govern that working set.

Row budget: 10,000 rows

A hard cap on the downloaded working set. A workspace whose window resolves to more rows is rejected before any enrichment work — the dashboard shows an error instead of a partial grid.

History window: 120 days, 12 months, or 36 months

120d = 120 days, 12mo = 365 days, 36mo = 1,095 days. Workspaces that have not chosen one run on the platform default of 120 days.

The window is not a per-user preference. It is a workspace setting at Settings → Reporting defaults, described there as: it sets how far back completed shipments stay loaded in the live dashboard for everyone, dashboard date filters cap at this window, and larger windows can exceed the 10,000-row limit for large workspaces. Only a tenant admin sees the History Window select and the Save Reporting Default button; everyone else sees the current value as read-only text.

The window does not hide open work. As the toolbar popover puts it, the working set includes all open shipments plus returned shipments from the selected window. Shortening the window drops closed history, never live containers.

Reading the history chip and the freshness line

The toolbar carries a compact chip like Dashboard history · 120d · 4,231. Open it for the Local dashboard history popover: the coverage sentence, an as of time, and a Change history window in Settings link.

At the right end of the same row, the dashboard states its freshness as LongShorty data as of 4:05 PM EDT. LongShorty is the worker that signs into terminal, rail, and steamship-line systems and writes back container milestones. When it produces newer data while you are working, the label is replaced by a button — Apply 12 updates from LongShorty — with a Detected time beside it and a tooltip breaking the change into changed, new, and removed counts. Your current rows stay exactly where they are until you press it, so a row cannot move out from under your cursor mid-task.

Troubleshooting