- 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 08:50 AM
Now, I did just notice that the order of the two maps was the same, so I changed the asset one to 10 and left config at 100. I have another set of data to load, so I will see if this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2014 08:56 AM
Ok. Good luck! Keep us posted!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2014 09:30 AM
That did not fix the issue either, but I have another idea of something to try. I will keep you posted and thanks again Ben for all of your help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2014 12:08 PM
Figured it out - for some reason, the state/substate is much more sensitive now when coalescing. If the value is not exactly a match then it doesn't recognize the value correctly, and does not fully put the asset "in stock" or "retired".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2014 12:20 PM
You are coalescing on state/substate?
You can determine behavior for when it is not an exact match in the "Choice action" field in the map (Creating New Transform Maps - ServiceNow Wiki). If you remember from class (I know... ages and ages ago), we imported some bad states where they were In Stock rather than In stock. We just had it import in class, but Choice action can prevent that. So if I understand correctly here, what you are actually seeing is that the entire row is ignored if those do not match exactly? I'm not sure how that is causing the Assigned to to not stay synced between Asset and CI, but it is a start here...
