- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2017 09:00 AM
Hi-
I have some questions about field mappings between the asset and CI tables. Our managers want custom choices in the hardware status dropdown (in CI), and in turn want those mapped to the asset table correctly. The choices I can modify, however, I cannot modify the mapping, as it is out of box, and un-editable. As an example, they want a Hardware Status of 'Spare' (to designate a spare pc), and want that mapped to In Use for the Asset. Is there a way around this? It won't let me create a new mapping, because the In Use mapping is one already used out of box. Any help is appreciated!!
Solved! Go to Solution.
- Labels:
-
Enterprise Asset Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2017 09:51 AM
Unless you are indicating that all CI records that are in use assets are spares from the CI side I think you would run into issues on keeping the sync going. Once the asset changes it might be troubling to know what status the CI should keep/have.
Another option for your scenario would be to add a field on the CI record called Function. This might be a choice list field that has values such as spare, loaner, dedicated, field. The state would still be in stock or in use, but with a field indicating the function you would not have to alter the OOB behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2017 09:51 AM
Unless you are indicating that all CI records that are in use assets are spares from the CI side I think you would run into issues on keeping the sync going. Once the asset changes it might be troubling to know what status the CI should keep/have.
Another option for your scenario would be to add a field on the CI record called Function. This might be a choice list field that has values such as spare, loaner, dedicated, field. The state would still be in stock or in use, but with a field indicating the function you would not have to alter the OOB behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2017 10:23 AM
I think the only Asset states we will be using are In Use, Retired, and Missing. Given this, is it possible to create the sync that I first mentioned?
I think the Function field would be beneficial, however, I have a feeling our managers would veto this.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2017 01:17 PM
I was going to weigh in but I see Jake has responded to you. You are in good hands Jamie. Best of luck in your deployment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2017 06:22 AM
OOB you are not able to alter these states, but only add new ones.That is partly the reason i would move towards the new attribute that indicates what the CI is being leveraged for outside of the state of In use.