When I navigate to my csv file at D:\David\Documents\Users.csv to upload, the navigator automatically uses C:\fakepath\Users.csv
If I create a directory "c:\fakepath", the upload still fails with 'Attribute Code of User not found'
I have populated the Code columns in the csv file, which was originally downloaded from Openmaint.
How do I get around this?
Regards
We suggest you check the CMDBuild User Manual, page 73.
For reference fields, the Export function extracts the Description column which is the most significant, while the Import function expects the Code column that is usually unique, so they are different information.
CMDBuild Team
My codes are unique.
The CSV import forces everything to come from c:\fakepath (the browse function is broke, at least under Google Chrome)
As far as I can tell, Openmaint is not even finding the file, then reports a bogus error.
Previously Tecnoteca wrote:
We suggest you check the CMDBuild User Manual, page 73.
For reference fields, the Export function extracts the Description column which is the most significant, while the Import function expects the Code column that is usually unique, so they are different information.
CMDBuild Team
As result of our test all works fine. "Fakepath" is a modern browser privacy/security feature that prevents JavaScript from knowing your file's local full path. This feature doesn't modify upload behaviour, because is just a browser trick.
CMDBuild Team
Previously David wrote:
My codes are unique.
The CSV import forces everything to come from c:\fakepath (the browse function is broke, at least under Google Chrome)
As far as I can tell, Openmaint is not even finding the file, then reports a bogus error.
Previously Tecnoteca wrote:
We suggest you check the CMDBuild User Manual, page 73.
For reference fields, the Export function extracts the Description column which is the most significant, while the Import function expects the Code column that is usually unique, so they are different information.
CMDBuild Team