Blog

Check Configuration Item Exports for Relations

July 4, 2020

Carlyn Manly

2 Min Read

Click To Explore

The configuration items export files now have an extra column. This column is called ‘Has CI Relations’. It indicates whether a configuration item (CI) is related to any other CIs. This column was added to make it easier for developers to use the data in the Xurrent CMDB as the source used to automate the maintenance of CI relations in other systems.

Configuration items export file with Has CI Relations column

Now that this column is included, these export files can be compared on a daily or hourly basis to check whether a CI’s relations have been removed.

In the past, it was not possible to perform an export of the CI relations that were updated in, let’s say, the past 24 hours to check whether a CI’s relations were removed. That’s because CIs without relations are not included in a CI relations export file.

Also, if all CIs that were updated in the past 24 hours were exported, it would not be possible to see if a CI’s relations were removed, as the relations are not included in a configuration items export file. That’s because the CI relations are separate records that include the relation type.

Because the ‘Has CI Relations’ column will have changed from ‘TRUE’ to empty after all the relations of a CI have been removed, it is now relatively easy for an automated script to figure out that the CI’s relations also need to be removed in the other system.

Partners

A Note From the Road: What SPARK Taught Me About Time

During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

3 Mins

July 1, 2026

Service Management

How Long Should ITSM Implementation Really Take in 2026?

Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.

8 Mins

May 30, 2026