Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

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

Limitation propagates to newly cloned view

Updated December 1, 2016


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.


  • NPM 11.5.2
  • NPM 11.5.3
  • NPM 12.0


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



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




Last modified