- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2023 09:34 AM
Hello,
I'm doing some testing with two CIs, a computer and a printer. In the CI records, I have the printer relationship set as a child of the computer. If I look at the asset records for each device I don't see any type of relationship, which is kind of what I expected. However, I'm wondering if there is a related list or a field I can add to the form that would allow me to see the relationship without going to the CI record?
I know I can add the parent field to the asset record and then tie the printer to the computer that way, however that is then a manual effort. If we are already manually tying the two together in the CI record, it makes more sense just to use the reference field to go to the CI record and view the relationship from there. But if there is a field, related list or something else I'm missing that will automatically show the relationship in the asset record, that would be great.
TIA!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-26-2023 04:29 AM
Relationships are relevant for CIs only. CIs are primarily for the purpose of managing operational and relationship information. Assets are for the purpose of managing financial, contractual and warranty information. Relationships are NOT applicable for assets. Any required relationships that you need to capture should only be done between the CIs which are linked to those assets.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2023 11:57 PM
Hi,
Sounds to me that you are mixing two diffent things. It's CI Relationships, not Asset Relationships. The CI relationships are part of the CMDB and show dependencies between CIs. Asset records have a totally different purpose and I would not recommend combining their functionalities.
As you wrote "it makes more sense just to use the reference field to go to the CI record and view the relationship from there", In my opinion Yes, that is how it should be done. When working with CI relationships it should be done from the CI not the Asset.
So, viewing the CI relationship from the Asset may not be that easy but the data is there so you should still be able to build logic on it.
Regards,
Niklas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-26-2023 04:29 AM
Relationships are relevant for CIs only. CIs are primarily for the purpose of managing operational and relationship information. Assets are for the purpose of managing financial, contractual and warranty information. Relationships are NOT applicable for assets. Any required relationships that you need to capture should only be done between the CIs which are linked to those assets.