Knowledge Base
How can we help? 👋
All Categories
Data Collection & Input
Dismissing warnings across assets and portfolios

Dismissing warnings across assets and portfolios

Suppress warnings that don't apply to an asset or portfolio with a recorded reason. Dismissals are tracked, reversible, and stop counting toward data completion.

Last updated on May 15, 2026

Purpose of this article

Some warnings don't apply to a given asset or portfolio. A certification flagged as potentially expired but intentionally kept on file. A meter that legitimately reads zero because there were no tenants. A meter start date that precedes ownership because you've retained pre-ownership data for like-for-like benchmarking. Instead of leaving these as permanent noise, you can dismiss them with a recorded reason. This article explains how to dismiss warnings from each surface, how dismissal scopes work, and how to review and reverse them.

Before you start

  • Available to users with edit access to the portfolio.

What dismissing does

Dismissing a warning hides it from the warnings list and removes it from the warning count that contributes to Scaler Data Completion. The warning is not deleted. It's archived to a Dismissed tab with the user, timestamp, and optional reason, and can be reversed at any time.

Dismissals are scoped:

  • By asset or portfolio: the dismissal applies to one asset, or to every asset in the portfolio (including assets added later).
  • By field or rule: dismissing from a specific field popover suppresses only that field. Dismissing from the Alert Overview suppresses the rule across every matching field or meter on that asset.
  • By framework: dismissing a warning on Scaler does not affect GRESB, and vice versa.
  • By resource tab: dismissing a "consumption is 0" warning on an energy meter does not silence the same rule on water or waste.

Where to dismiss a warning

There are three surfaces. Use whichever fits the situation.

From the field directly (Input Portal)

Use this when you spot a warning while editing data and want to suppress just that field on that meter.

  1. In the Input Portal, hover over the warning icon on the field.
  1. Click the × in the popover.
  1. Add an optional reason.
  1. Confirm.

This dismisses the warning for that specific field on that specific meter, at the asset level.

Notion image
Notion image

From the asset Alert Overview

Use this when you're reviewing all alerts on a single asset and want to suppress a warning rule across every matching field on that asset.

  1. Go to Data Collection Portal → Portfolio → Asset → Alerts.
  1. Open the Warnings tab.
  1. Click Dismiss on the row, or multi-select rows for bulk dismiss.
  1. Add an optional reason.
  1. Confirm.
Notion image

From the portfolio Alert Overview

Use this when a warning rule applies across many assets and the dismissal should hold for the whole portfolio.

  1. Go to Data Collection Portal → Portfolio → Alerts.
  1. Open the Warnings tab.
  1. Click Dismiss on the row, or multi-select rows for bulk dismiss.
  1. Add an optional reason.
  1. Confirm.

Portfolio-wide dismissals apply to every asset currently in the portfolio and to any asset added to the portfolio in future.

Portfolio-wide dismiss and undismiss run in the background because every asset re-validates. The row shows "Dismissing across portfolio…" while the operation completes. You can navigate away. If the operation fails, the row shows a red Failed badge and the action can be retried.

Notion image
Notion image

Reviewing dismissed warnings

The Dismissed tab

Both the asset and portfolio Alert Overviews include a Dismissed tab. Each row shows:

  • Scope: Asset or Portfolio-wide
  • Section and Field the warning relates to
  • The original warning text
  • Reason entered at dismissal
  • Dismissed by (user) and timestamp
  • Undismiss action

The portfolio Dismissed tab also lists asset-scope dismissals, with the asset name and a link showing which assets are affected.

Notion image

Show dismissed warnings toggle

On any Input Portal sheet, the Show dismissed warnings toggle at the top of the sheet reveals which fields have suppressed warnings. Off by default to keep the regular flow clean.

When enabled:

  • Asset-level dismissals show a muted or strikethrough indicator on the field.
  • Portfolio-level dismissals carry a P flag with a "Manage portfolio dismissals →" link back to the portfolio Alert Overview.
  • Section headers show an "N dismissed" badge so you can see at a glance which sections have suppressed warnings.

Reversing a dismissal

To bring back a dismissed warning:

  1. Open the Dismissed tab on the relevant Alert Overview (asset or portfolio).
  1. Click Undismiss on the row, or multi-select for bulk undismiss.

The warning reappears in the Warnings tab and counts toward data completion again. Portfolio-wide undismiss runs in the background, like portfolio-wide dismiss.

Notion image

Audit trail

Every dismiss and undismiss event is recorded with:

  • The user who took the action
  • Timestamp
  • Reason, if entered
  • Scope (asset or portfolio-wide)

Dismissals are visible on the Dismissed tab and are recorded in the Audit Log alongside every other data change. For audit and assurance purposes, the recorded reason is the defensible explanation for why a warning was suppressed.

For broader audit context, see Audit features in Scaler.

What can and cannot be dismissed

Alert type
Dismissible?
Errors
No. Must be resolved at source.
Missing data
No. The required field must be filled.
Blocking issues
No. Must be resolved to generate a report with 100% data completion.
Warnings
Yes.

If you find yourself wanting to dismiss an error or missing-data alert, the underlying data must be fixed at source. Errors and missing data block calculations and reports, and cannot be suppressed.

Common scenarios

A certification has expired but is intentionally kept on file

Dismiss the "certificate may no longer be valid" warning portfolio-wide with a reason like Renewal in progress or Kept for historical reference.

A meter legitimately reads zero

For example, no tenants in a period, or solar production fully redelivered to grid. Dismiss the "consumption is 0" warning at the asset level with the operational reason.

A meter's start date precedes the asset's owned-since date

Dismiss the "meter start date earlier than owned since" warning portfolio-wide with a reason like Pre-ownership data retained for GRESB like-for-like points.

Troubleshooting & common mistakes

  • Dismissal didn't take effect right away → Portfolio-wide dismissals run as a background job. Wait for the spinner to clear. If it shows a red Failed badge, retry.
  • Dismissed warning still showing on a different framework → Dismissals are framework-scoped. A Scaler dismissal does not silence the same rule on GRESB, and vice versa. Dismiss separately on each framework if needed.
  • Dismissed an aggregation warning and it disappeared from every year → Aggregation warnings on reporting-data rollups currently dismiss across every reporting year the aggregation touches.

Additional resources

Did this answer your question?
😞
😐
🤩