Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Limitation propagates to newly cloned view

Limitation propagates to newly cloned view

Updated December 1, 2016

Overview

This article provides brief information and steps to resolve the issue when a view with limitation is cloned.  The limitation is propagated to a new clone view.

 

For example, when view1 is clone [View1(2), View1(3) and View1(4)]. The limitation is copied to all these views.
By default, the limitation should NOT get copied or cloned.

Environment

  • NPM 11.5.2
  • NPM 11.5.3
  • NPM 12.0

Cause

The issue occurs after an upgrade from NPM 11.5.3 to NPM 12.0.

Resolution

Workaround:

1. Delete the limitation first for the view you need to clone. 
2. Put the limitation back.

 

 

 

Last modified

Tags

Classifications

Public