Skip to content
English
  • There are no suggestions because the search field is empty.

Not All Assets Are Included in the Report

Understanding why some assets may not appear in generated reports.

Overview

When running a report, users may occasionally notice that not all assets are being included in the output. This behaviour is expected under certain conditions and does not necessarily indicate an error.

Perspio only includes assets that:

  • Are visible to the user (based on Security Group permissions).

  • Are active and unarchived.

  • Have telemetry or operational data relevant to the selected report.

  • Belong to an asset schema supported by that specific report type.

This article outlines the most common reasons assets may not appear in reports and how to verify or correct each condition.


Common Reasons for Missing Assets

1. Security Group Restrictions

Perspio uses Security Groups to control user visibility across tenants and assets. If an asset belongs to a group that you do not have access to, it will not appear in your reports—even if it is active and producing data.

How to Check:

  • Navigate to Security Groups under the Administration or Settings section.

  • Confirm that the assets you expect to see are included in your assigned groups.

  • Request administrator access or group inclusion if necessary.

Tip: This restriction ensures that sensitive or customer-specific assets are not shared beyond their intended audience.


2. Archived Assets

Assets that have been archived are excluded from live reports by default. This applies to assets that have been intentionally retired, replaced, or deactivated for maintenance purposes.

How to Check:

  • Go to Assets Inventory> Disabled Assets List and to display archived assets.

  • If the asset appears there, it must be unarchived before it can appear in reports again.

Note: Archived assets retain their historical data, which can still be accessed through custom data queries or historical reports if required.


3. No Data for Selected Report Type

Some reports, such as Utilisation Summary, Temperature Compliance, or Geofence Movement, rely on specific types of telemetry data.
If an asset has not generated the corresponding data during the selected time period, it will not appear in the report output.

Example Scenarios:

  • An idle or unused asset will not appear in a Utilisation or Activity report.

  • A device that has not transmitted location data or doesn't move between Geofences  will not appear in Geofence Movement.

  • Assets without temperature sensors will not appear in Temperature Compliance reports.

How to Check:

  • Verify device connectivity and recent telemetry under Device Health.

  • Ensure the reporting period includes a timeframe where the asset was active.


4. Unsupported Asset Schema

Each report is designed to process data from specific asset schemas (such as Refrigerated Trailer, Vehicle).
If an asset does not match a supported schema, it will be excluded from that report.

How to Check:

  • Navigate to Asset Settings > Schema.

  • Review which schema is applied to the asset.

  • Check the Report Description on the Snapshot tab to confirm which schemas are compatible.

Example:
The Temperature Detailed report supports schemas such as:

  • Refrigerated Truck Schema

  • Generic Senquip Schema

  • Refrigerated Trailer Schema

If the asset uses an incompatible schema, it will not be included in the report.


Troubleshooting Checklist

Before contacting support, review this quick diagnostic list:

Step Check Action
1 Security Group Ensure you have access to all relevant groups.
2 Asset Status Confirm the asset is not archived or inactive.
3 Data Availability Verify the asset has produced telemetry data during the selected period.
4 Schema Compatibility Confirm the asset schema matches the report type.
5 Date Range Widen the selected period to capture recent activity.

Summary

When assets are missing from reports, the cause is typically one of the following:

  • Restricted access (Security Groups).

  • Archived or deactivated status.

  • Lack of data due to inactivity.

  • Unsupported schema configuration.

By confirming each of these elements, users can ensure consistent and accurate reporting across the platform.