Data Manager objects vs attributes

[Ryan Bullock]

I'm a bit new to CMDB and with Data Manager becoming available am trying to import from CrowdStrike Falcon. The main thing I am trying to understand right now is how Data Manager determines what are actual objects vs just attributes of an object? During mapping, how do primary key, secondary key, or ignore play into the creation of objects? With the 50k object cap in mind before the usage cost starts to apply, I'd like to understand how the 4.7k records imported with dozens of columns are going to translate to objects.

[Fabian Lim · Accepted solution]

Hi @Ryan Bullock

I don't think you can determine that from Data Manager.  You will have to first create another Asset Schema that holds those objects, so that when you import the cleansed data from Data Manager, it links them properly (this is done manually).  The problem right now is that the functionality to export data manager objects is not possible, so it's hard to envision how you would be able to determine whether an object has an object within it for a relationship.  

I hope this makes sense.

Regards,

Fabian

[Ryan Bullock]

Thank you for the reply. After going through more of the process I see that once I have mapped, cleansed, and imported in Data Manager I can then export that data. On import to Assets, I can then map to Assets objects, so we will work on creating a schema to control the number of objects and what is an object vs an attribute.