Import CMDB Relationships and Create Two-way Linkages in AssetSonar

Import CMDB Relationships and Create Two-way Linkages in AssetSonar

AssetSonar’s CMDB provides a complete repository of linkages between configured items to eliminate the challenge of limited visibility and delays in ticket resolution. You can get in-depth visibility through relationship mapping of the dependencies of a CI and how they interact with each other, thereby getting support in ITSM workflow, through prompting actions with maximum efficacy — resulting in quick service delivery and improved employee productivity.

Furthermore, access to a consolidated IT asset landscape map reduces compliance risks and helps simplify planning for audits.

Within AssetSonar, you get some commonly used Asset-CI relationships that you can readily create. The outgoing and incoming relationships that AssetSonar provides by default help you in easily adding items from the Asset Details page.

You can also import multiple CMDB relationships from your system with the help of our import relationships functionality in AssetSonar. You can do so by importing an Excel or CSV file and then mapping out the columns correctly to create the right relationship. Let’s dive deeper to see what columns need to be mapped on your Excel sheet for a successful import to AssetSonar.

  • Outgoing Object Type: You need to define the item (asset, asset stock, inventory etc.) from which you are creating the relationship. In this scenario, we are creating the relationship from an IT Asset.
  • Outgoing Object ID: This would entail the unique ID of the asset that you are creating a relationship from. This can be your asset’s sequence number or its AIN number.
  • Outgoing Relationship Name: This field allows you to define the type of relationship your Outgoing Object Type (which is an asset in our case) is to have with the incoming object type. For example, if your asset is being connected to another asset, the Outgoing Relationship Name would be ‘Connected to Item’.
  • Incoming Relationship Name: Here you can define the type of relationship your Incoming Object Type is creating with the Outgoing Object Type. For example, if a relationship is being created between your laptop and its mouse or keyboard, the Incoming Relationship Name would be ‘Connected to item’.
  • Incoming Object Type: As your Outgoing Object Type is an asset, your Incoming Object Type can vary between an asset, asset stock, inventory, member, vendor, location, and so on.
  • Incoming Object ID: Similar to Outgoing Object ID, you will need to add the unique identification number of the second object you are creating a relationship with.
  • Incoming Object Parent Type: If you are creating a new relationship between two items where the Incoming Object is part of a sub-group, you will have to mention the name of its Group in this field. Similarly, you can also add this field for Outgoing Object if the chosen asset is part of a sub-group. Incoming Object Parent Type is an optional field and you will only need to use this field if you are selecting a Sub-Group as your Incoming Object Type.
  • Incoming Object Parent ID: This is an optional field that is used in the case of Subgroup. Mention the name of the Parent Group that contains the Subgroup which has the incoming object.

Here is a glimpse of a sample file containing all the above-mentioned fields:

Notes:

  • AssetSonar currently allows you to create relationships only where the outgoing object type is an asset.
  • Outgoing and Incoming Relationship Names are matched against the relationships that exist in the system. If no relationship is found, then AssetSonar creates a new one for you. You can also create and view a custom relationship by following this path.
  • Please note that the type of every relationship differs with every module as it is dependent on the unique identifier for that particular object. Here is a list of supported objects and their unique identifiers:

Once you have mapped out all the relevant relationships in your Excel sheet, you can then import it to AssetSonar. Follow these steps for a successful import:

  1. From an item’s detail page, click on the ‘Relationships’ tab as shown below:

2. Now click on the dropdown button beside ‘Add Relationship’ and then click on ‘Import Relationships’.

3. A new webpage will open up. Click on ‘Choose File’ and then select the already created file from your machine.

4. Once selected, click on ‘Upload and Proceed’ and you will be redirected to a new page so you can map the fields under the right columns accurately. Here is a glimpse of the webpage where you can map your columns:

5. If you have added a relationship type that doesn’t exist in the system already, then click on the checkbox mentioning ‘Create new Relationship Type if it doesn’t already exist in the system’ as shown below:

6. After mapping out the columns successfully, click on ‘Proceed’ and a new window will open up as shown below:

You would be able to preview all the relationships you have just imported.

If there has been an error while mapping the columns, an error message will appear on the top as shown below:

You will also be able to view how many relationships haven’t been imported due to errors. Here is a glimpse of the error messages that you might if there have been errors in your Excel sheet or if you have made a mistake during mapping columns:

7. Click on ‘Import’ to complete the relationship building process. You would be able to view the imported relationships on an item’s detail page, under the Relationships tab as shown below:

AssetSonar also allows you to export your relationships as PDF or CSV files. Click on the ‘Export’ button in the relationships tab to download the details of all relationships specified to that item.

Here is a glimpse of an exported PDF copy of an item’s relationships:

Read more: Gain Clear Visibility Into Your IT Asset Dependencies With CMDB

About AssetSonar

AssetSonar is a powerful ITSM tool used by tech organizations and businesses all over the globe. Sign up today for a free 15-day trial.

For more assistance, drop us an email at support@ezo.io. You can also visit our blog for detailed support posts.