Version reports are only useful if they describe the PCs the team actually cares about.
Old records can create confusion.
A PC might exist in datastore history but no longer be part of the current Portal 2 dashboard view.
For the A9X Software Versions page, we tightened the data flow so the report starts with the current Portal 2 PC list.
What that means
The A9X Software Versions view does not enumerate old datastore computers.
Instead, it builds rows from the PCs already shown in the selected fleet dashboard.
Then, for each of those PCs, it asks datastore for the matching ledger by the exact group, vessel, and MAC address.
If a PC is not in the current dashboard list, it does not appear in the A9X version report.
Why that matters
Fleet inventories change.
Computers are replaced.
Records can remain in backend systems longer than the operational view needs them.
A version table should not make a support engineer wonder whether a row is current or historical.
By scoping the report to the dashboard PCs first, the portal keeps the report aligned with what the user is already reviewing.
Bottom line
The A9X Software Versions view is now current-fleet focused.
It uses datastore for authoritative version fields, but it only reports against PCs that Portal 2 is actively showing.