- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-24-2014 10:03 AM
Does anyone know why at times the assigned to person will be removed from an asset record but not the related CI record? The state/install status are correlating fine, but at times, the assigned to person on the CI is not automatically removed like it is on the asset record.
I have a work around in place - running a report and removing the values manually, but I'm wondering if this is a bug?
Thank you,
Melinda
Solved! Go to Solution.
- Labels:
-
Enterprise Asset Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-26-2014 01:05 PM
No, you are correct. if the status switches from In use to In stock, then the Assigned to field does automatically clear itself out. Based on our findings above, though, this is not also clearing out the Assigned to on the CI, though. I may have to check and see if there is some logic behind why this is the case...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-26-2014 12:32 PM
You are right. So, it is creating new values, but I don't think it should because I am very careful to make sure it says "In stock" not "In Stock" and "Pending disposal" not "Pending Disposal". Instead of setting the asset with a substate of "pending_disposal", which is how it looks on a report it is creating a new value of "Pending disposal". For some reason it's not seeing this substate value as a match.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-26-2014 12:38 PM
It's removing the assigned to value from the asset record/table but not from the CI record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-26-2014 12:46 PM
Interesting! On a whim, I thought I would try deleting the Assigned to value on an Asset manually. When I did this, it did not remove the Assigned to on the CI. I then tried the reverse and experienced the same thing. Setting a value automatically updates these so they match, but deleting the value does not clear out the corresponding value in the associated record. I have changed this information innumerable times, but I have never just cleared out the field to see what happens. I wonder if this is by design to keep you from completely losing that data by accident.
So with this in mind, is your import set to import blank Assigned to data?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-26-2014 12:51 PM
No, it is not - the idea/understanding I had is that if the status went from Installed to In Stock that the "Assigned to" field would automatically clear itself out. Maybe it's been doing this longer, and I'm just losing it? 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-26-2014 01:05 PM
No, you are correct. if the status switches from In use to In stock, then the Assigned to field does automatically clear itself out. Based on our findings above, though, this is not also clearing out the Assigned to on the CI, though. I may have to check and see if there is some logic behind why this is the case...
