Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Dependencies added through PowerShell do not show up in Admin > Manage Dependencies

I'm pretty fresh to using the SDK and I'm running into a perplexing issue when trying to create dependencies. When running this line, it executes successfully and I can see it by querying orion.dependencies in SWIS. However, when I go to the Admin > Manage Dependencies page it is nowhere to be found. If I try to create a dependency in the GUI with the same name & parent/child objects, it gives me the error "A dependency with the same objects already exists. Please change the objects of this dependency." I'm running NPM 2020.2 for reference.

Anyone have insight as to what I'm missing? Thanks in advanced!

New-SwisObject $swis "Orion.Dependencies" @{Name="$Sitename test Dependency";ParentUri="$($ParentGroupUri)";ChildUri="$($ChildGroupUri)";AutoManaged=$false;ParentEntityType="Orion.Groups";ParentNetObjectID="$($ParentGroupUri.split('=')[1])";ChildEntityType="Orion.Nodes";ChildNetObjectID="$($ChildGroupUri.split('=')[1])"}

Find more posts tagged with

Accepted answers

All comments

mrxinu

If you create another, unrelated, dependency in the GUI does it the one you created with the API show up in the GUI? I'm trying to determine if it's the same behavior @shuth was seeing in another environment.

mesverrum

When it comes to groups and dependencies I have found the GUI can be extremely sensitive in a way that the underlying application isn't. What I mean by that is I have done all kinds of hacky things in the API and SQL actions and inserted objects and they seemed to work the way i expected but then the GUI either didn't show them or displayed them with glitches. When I had run into that I found that if I did a character by character comparison between what I made and what the GUI makes for the same objects it would be exactly the same except for some seemingly trivial thing like a capitalization difference, or some minor difference in white space. It has happened to me so often that it is my immediate thought now, take whatever I have in SQL and drop it into notepad++ with the show all special characters enabled and then blow it away, try to create the same object in the GUI and then copy that and see where I changed a character. So far I have always found *something* I did "wrong" and when I got my code to match the GUI way then my problems cleared up.

jarren

After using the API to create a couple groups and the dependency, I created two separate groups and a new dependency in the GUI. Only the dependency created in the GUI showed up. I also tried creating groups in the GUI and then creating the dependency in the API and that did not show up in the GUI either.

jarren

I found something else that is interesting. If I go to "https://localhost/Orion/Admin/Dependencies/Add/Default.aspx?DependencyID=451" after creating the dependency using the API (Using the DependencyID I get from SWIS). The GUI walks me through as if I'm editing the dependency. The Parent and Child groups are already pre-selected. After clicking through and saving, it shows up in the list correctly. The SWIS query results don't look any different before or after this.

jarren

Excuse my ignorance on the subject, how would I go about finding the underlying commands that the GUI uses to create the dependency? When I compare an API-Built dependency with a GUI-Build Dependency using a SWIS query, I'm not seeing any difference in the properties except for the group containerIDs. I tried what you suggested but didn't see any special characters that were out of the ordinary in my script.

mesverrum

Trial and error? I never have seen a convenient reverse engineering method