Assigned to value removed from Asset but not Config

lileem09
Kilo Expert

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

1 ACCEPTED SOLUTION

Community Alums
Not applicable

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...


View solution in original post

20 REPLIES 20

Yes, I am running two transform maps against one import; the first to run is against the asset table and the second is against the computer table in config.   Good suggestion, but I checked both transform maps, and they both have the "Run Business Rules" box checked.


Hi,


I face the same issue like "Assigned to value removed from asset but not in config" we dont use any transform map.Is there any way to fix this?


lileem09
Kilo Expert

Looking at individual records, what is happening is when the transform map runs for Asset, the assigned to value is removed, but it is put back when the transform map is run against Computer/Configuration table.


Community Alums
Not applicable

But it is coming from the same source? Is the Assigned to mapped in both transform maps?


Yes, both of the transform maps use the same source.   No, the assigned to field is only mapped in the Asset transform map.



The odd part is that this just started happening a month ago, but I've been using these same maps for six months.   I'm wondering if it has something to do with upgrading to Eureka.