CMDBuild Forum

Import Bug? - Multi-level lookups

Sorry this may be a re-submit but my original post did not seem to show up.

 

I have setup a multi-level lookup covering off a brand/model relationship in my design. For example if you select HP the child lookup is filtered to just HP models. The card displays this as "HP - Elitebook" or "Dell - Latitude" in the relevant field.

 

I am seeking to import an enormous database of systems and it seems the import utility does not work properly with multi-level lookup data. I will post this in precise detail but just want to find out first if there are known bugs / limitations of the import utility specifically around multi-level lookup fields.

Unfortunately at this time that is a limitation of the CSV import function.

We will extend the function in a later version (our wish list is already very long ...).

 

The solution that we use in these cases is to write an insert SQL query and run it from pgAdmin.
But this can be
a critical operation (the database may become inconsistent) and is recommended for advanced users.

 

CMDBuild Team