Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

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