Clear data in Analysis

[Daniel Cotter]

We've discovered that once important data, it's permnanent.

In our testing we've put data into data manager without correcting all of the data.

Is there are a way to remove data once its been cleansed and imported?

We've deleted DS's although that only applies to the import element.

There doesn't seem to be away to manipulate the data once it's in? If this is the case how do we reset the already processed data in Analysis?

[Hun Chan · Accepted solution]

Hi Daniel, 

You mean once data is "imported", it is permanent. Is my assumption correct? I don't believe once the data is imported, it is permanent. 

Which data source has the incorrect data? Which data source has not been properly mapped and incorrect rules have been applied?

You can remove/delete this data source in question by going to Data Manager->Settings->Select the data source to delete (click on the "..." button and select delete). The system will ask you to confirm that you intend to delete the selected data source. Press the DELETE button to confirm. 

Reimport all the data sources again and you will find that the data source and the data related to the data source you deleted in the previous step should be removed. You can confirm that the data source has been deleted by going to Analysis and selecting the relevant (impacted) object class (e.g. compute, network, people, peripherals, etc.).

Regards,

Hun

[Karyn Findlay]

Hi @Daniel Cotter 

Data Manager is not only about getting data into an Assets Schema, it is also about ensuring that your data remains Complete, Current and Correct.  For this reason, once a records is clean and correct, we don't remove them from Data Manager unless it is no longer in the source.

Let me explain using a couple of examples.

Example 1: 

A device is correctly showing in your ITAM/ITSM tool with the correct operating system (OS).  Your EUC team start upgrading the operating systems from Windows 10 to Windows 11.  The device that was previously reporting the correct OS is now wrong.  By using OS as an important field, where any source has a conflicting OS, it can be flagged as un-verified and you can identify these records that need an update in your ITAM/ITSM tool.

Example 2:

A device is showing the correct status of In Use.  You noticed that the inventory day for the device is > 30 days old.  This can be flagged and you can see if the status is correct.  Was it returned to storage and should have an alternate status, is the user on leave for > 30 days and its still correct, is the user having trouble connecting to the network and are therefore not getting their device patched?  These are all potential causes.

There are many more such examples as to why we continue to send through devices to Data Manager after they have cleansed and imported. 

This Community page does go through some of the use cases.: https://community.atlassian.com/t5/Assets-Data-Manager-f-k-a/How-Data-Manager-fits-into-your-organisation/ba-p/2686201