daraka ✭✭✭✭✭

SW Version is 2023.4.2 Confusion was caused due to logging in to SWQL Studio with the Orion (v3) Certificate option and testing PowerShell with a different account. I checked with our admin, and he verified that the account has a SAM limitation. I tried this with an account with full access, and it worked perfectly. :)…

Hi @"KMSigma.SWI"you are correct. I connected the SWQL studio Information Service with the credentials that I used to connect in Connect-Swis function, and It gives an empty result for the query. Thanks for the shared formatted query and the guidelines 

Hi @"kelvin.owiti"thanks for your answer.

You can try the import and export options in the Manage Alerts section. Not sure how to change AlertRefID values when you import back. eg: <AlertRefID>f52e699e-8ef1-4dff-a686-4b54d71e591e</AlertRefID> <d2p1:PropertyValue>301a76fc-35ae-48a4-b576-1968d3f1bcd4</d2p1:PropertyValue>

Hi, I tried to revert my 'Node Details' views to the default state by exporting the default views from the freshly installed platform and importing those into the production platform. It gave me the following error message in PowerShell. However, it changed my node views back to default. Any ideas? Thanks! Platform…

Hi stuartd yes you are correct!

Wha is the error that you are getting ?

I think InterfaceLastChange is the one that you have to use for status change. Better do some manual changes in the test interface and verify the same.

Further to marcrobinson answer, you can refer to the following link for more details : https://documentation.solarwinds.com/en/success_center/npm/content/npm-netpath-requirements.htm

Hi, Please refer to this Post: https://thwack.solarwinds.com/product-forums/the-orion-platform/f/report-lab/98777/integrating-solarwinds-with-red-hat-openshift You may contact robert777 for more insight.

Thanks for your feedback!

Is this a known bug in the 2023.2.1 version?

Hi please check this post, similer to your case : thwack.solarwinds.com/.../npm-create-servicenow-incident-showing-warning-message-some-currently-selected-values-are-no-longer-valid

Thank you, @stuartd, for the guidance. I'll follow it accordingly.