Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2018Jan03 - Deletes > Do not use the same name for a web-based and legacy report in NPM 12.0

Do not use the same name for a web-based and legacy report in NPM 12.0

Table of contents
Created by Lori Krell_ret, last modified by Gerald.Prado on Jan 03, 2018

Views: 785 Votes: 0 Revisions: 4

Overview

Creating legacy versions of web-based reports sharing the same name can cause issues. If the web console locates a duplicated name for a report in a local file and a web-based report, the console throws a series of errors when displaying the report list.

 

Environment

  • NPM 12.0

Detail

When creating a copy of a web-based report, you should create the report as a web-based or legacy with a different name than the original report. The report list checks and displays a list of reports by name. If a legacy and web-based share the exact same name, the web console displays errors.

 

Always give a legacy report a different name than a web-based report to keep the issue from occurring.

 

 

 

Last modified

Tags

Classifications

Public