Skip to main content

Troubleshooting Asset List and Detail

Summary​

This page covers reports that an asset is missing from a list or that list content looks unexpected. Asset lists are tenant-filtered and loaded in full; there is no server pagination control exposed in the UI. There is no dedicated detail view in the portal. A missing asset in a list is usually a wrong-tenant or status-filter condition rather than lost data. Compatibility responses are monolith-shaped projections, so their field shape differs from native responses, which sometimes reads as "missing" fields when it is actually a shape difference.

Audience​

Support engineers, QA engineers, and developers investigating list content, missing rows, or projection-shape questions.

Symptoms​

  • An asset the user expects is not in the list.
  • The list looks shorter than expected or filtered.
  • A user asks where the asset detail view is.
  • Fields differ between the compatibility view and a native response.

Cause​

Scope​

This page covers list content, projection shape, and the absence of a detail view. Empty-list-due-to-tenant is shared with the tenant-context page.

Likely causes​

  • The tenant context is wrong or missing, so the tenant-filtered list omits the asset.
  • A status filter in the UI is excluding the asset's current status.
  • The user expects a dedicated detail view, which does not exist in the portal.
  • The response is a monolith-shaped compatibility projection, so the field shape differs from the native shape.

Resolution​

Safe diagnostics​

  • Confirm the tenant context matches the tenant that owns the asset.
  • Confirm no status filter is hiding the row, and clear filters to re-check.
  • Confirm the asset exists by listing assets for the tenant; the list loads in full, so the row should appear if the tenant and status align.
  • When comparing fields, note whether the response is the compatibility projection or the native shape before concluding a field is missing.

Validation​

  • Confirm the asset appears once the correct tenant and cleared filters are applied.
  • Confirm the projection shape matches expectations for the path used.
  • Confirm no detail-view expectation remains unmet in the ticket.

Evidence to Collect​

  • The tenant identifiers and any active status filter.
  • Whether the compatibility or native path was read.
  • A correlation identifier and timestamp.
  • The specific asset code expected but not shown.

Escalation​

Route list projection questions to the asset or backend team. Route portal filter and missing-detail-view expectations to the frontend team.

Source References​

  • microservices/src/asset-service/Api/AssetCompatEndpoints.cs
  • microservices/src/asset-service/Api/AssetEndpoints.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx

See Also​

Keywords​

asset list, projection, missing row, no detail view, status filter

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly