appvm | Nix-based app VMs - | Infrastructure Automation library

The fundamental problem in your code is that you have dedicated a pre-defined view model object to each of the user controls. This is really bad. A user control's data context must be left alone, for the client code (e.g. your main window) to determine, and to use for binding to specific properties that the user control exposes.

Unfortunately, there's not enough context in your question to provide a clear, complete answer. But to fix your issue, you need to do things differently:

1. First and foremost, "decouple" the view models you are using for your user control from the user controls themselves. Do this by adding dependency properties to each user control, and then letting the main view where the user controls are used decide what to bind to each of those dependency properties. Do not allow the user controls themselves to set their own data contexts.
2. Having done that, you may find that you can just use the same view model for the two user controls as for the main view. I.e. you'll set the main view's data context to the single view model, the user controls will inherit that data context, and you'll bind, for example, the TextboxText property to the appropriate declared dependency property in each user control. This way, that single property will represent state for both user controls at the same time.

One hopes that will be enough to get you back on track. If not, consider searching Stack Overflow for other questions related to view models and their relationships to user controls. For example, these questions:
Issue with DependencyProperty binding
XAML binding not working on dependency property?
WPF DataBinding with MVVM and User Controls

Other questions which don't address your scenario exactly, but which should give you some ideas for alternative ways to structure your view model(s):
MVVM : Share data between ViewModels
Sharing non control related data between WPF ViewModel and UserControl
Sharing data between different ViewModels
Sharing state between ViewModels

It looks like you are creating multiple instances of AppVm.
The button in View1 and the buttons of the navigation bar obviously don't bind to the same instance of AppVm.
Same applies to the CurrentView property: your content host binds to a different instance i.e. different property value references, than the CurrentView you are modifying in View1. Therefore changing CurrentView from inside View1 has no effect on the content host --> view never changes.
Make sure you always reference the same (shared) instance in the same context.

There are multiple ways to achieve this, based on the structure of your UI. Creating a Singleton of the view model class is by far the worst choice. Singletons should and could always be avoided.

The simplest solution would be to declare the view model as a resource in the App,xaml ResourceDictionary:

App.xaml
Resources defined in this file are globally available in any XAML context via the StaticResource markup extension resource dictionary lookup.

To display the data again outside of the table, you can just display rowData (I don't know the structure):

You should assing a list to the ip_list variable, not a string. You're expecting a list but you're assigning a string (that's technically fine, it gets parsed into a list with single string in it. ) and then a comma, which is the extra character.

Instead you should pass a proper list as a parameter, notice the 'array' / [] (square brackets) notation.

Assuming that you are using ES6.
Here's how you would find all the students taking a particular subject:

Until further notice(or someone comes up with something better), I am using (and it works, for me) the following patch in order to avoid any disk thrashing / OS freeze when about to run Out Of Memory and thus the OOM-killer triggers as soon as possible(max 1 sec):

Yeah Now Iam able to delete specific resource with below commands.

Well, with the errors that in your comment, I think you should set the subnet like this:

There's very little null checking in your code, which is where this is happening.

The best way to find the issue is to go to the Visual Studio tool panel

Debug → Windows → Exception Settings

and fully check the row labelled 'Common Language Runtime Exceptions'. When you run the code again, you should get more information about where the null exception is happening.