CMDBuild Forum

Import Using CSV Issue

Old Versions
#1

This might be a bug or a feature request. I am using CMDBuild 2.1.3

When importing data into a Class using a CSV file, attributes that use a Lookup are difficult to import because it does not use the CODE or DESCRIPTION fields rather it requires the DATABASE ID field to map correctly. This makes it difficult to import items because you don't know what that DATABASE ID for a specific Lookup item without looking at the actual database table.

For example if you have a Lookup table similar to below, in order to import data in a Class that uses this Lookup, you'd have to use the ID field. If I want to import POOR in Class attribute, I would have to put 1 on the CSV file instead of POOR.

 

ID Code Description
1 POOR This is Poor
2 FAIR This is Fair
3 GOOD This is Good
4 EXCELLENT This is Excellent
#2

Hello,

the proper way to prepare a CSV file to use the CSV import function is to place in the file the "Description" of the lookup attributes (and the "Code" of the reference attributes), as written in the User Manual (page 57).
Unfortunately, in version 2.1 was introduced the bug of expecting the "Id" instead of the "Description".
The bug has been fixed and the correction will be available within a couple of days with the new version 2.1.4
CMDBuild Team















 

#3
Awesome! Looking forward to the 2.1.4 Build.
 
Previously Tecnoteca wrote:

Hello,

the proper way to prepare a CSV file to use the CSV import function is to place in the file the "Description" of the lookup attributes (and the "Code" of the reference attributes), as written in the User Manual (page 57).
Unfortunately, in version 2.1 was introduced the bug of expecting the "Id" instead of the "Description".
The bug has been fixed and the correction will be available within a couple of days with the new version 2.1.4
CMDBuild Team