When changing the status of a parent asset, is the status suppose to cascade down to the child assets? If not, is there a way to do this without manually going into each child asset and changing the status?
Hi,
There is no cascading with a status is change when using a ticket type "Service Request", which you might have if you created a child ticket using a Task?
But I believe you can cascade status if you use problem and incident ticket types as shown at the bottom of this page: Manage problem and incident tickets - SolarWinds Worldwide, LLC. Help and Support
Additional you can't create Problem and incident tickets using a task.
regards
Chris
I was actually talking about parent assets, like a computer, and children assets associated with it, AC adapter, battery and such. When you change the status of the parent asset to retired, should it cascade down to the children assets?
Sorry I misread that badly !
Do you use an Asset Discovery connector? You might be able to work out something with that...
We use a parent asset number CF for child asset when we import them, which can be used to manage assets.
Although something worth looking into...
You can export to excel document and use the "Related Asset Sync Keys" column to work out which parents are retired, then change the children status to retire too in an asset import file, then re-import the updated children.
We do not use asset discovery connector. All of our new assets are imported in every semester. When a student leaves, their computer is set to a retired status so it will no longer show up in our inventory, but the child assets do not change. I guess I will have to download the asset export and manually change them.
