Updated: Dec 8, 2021
Some tips / Notes concerning the files used for data import:
When uploading excel files you don’t need to use special column delimiters or row delimiters
Make sure the data in your excel columns match the data type of the fields they are mapped to. For example all dates in your spreadsheet need to be stored as a date format in excel, if any are stored as text or some other format you will receive errors when trying to import your data
Currently we only support importing of dates using DD-MMM-YY, DD/MM/YYYY, or DD MMM YYYY format e.g. 10-Nov-10, 10/11/2010, 10 Nov 2010
If you are importing data as csv files you must use DD-MMM-YY format
The column heading text does not matter, the number of columns do not matter. As long as you have the mandatory columns covered you can load the data. The data loader will tell you which columns are mandatory.
You can keep your ID’s from the Source System in a Custom Field against the entity (Contact or Organisation) for tracing back an issue down the track. E.g. Source ID. Set visibility permissions on the Custom Fields Section to View only and for Super Users only.
If you are performing a data cleaning operation, but using Contact/Organisation Search or Data Mining Query, you should include the Contact or Organisation Id in your export from ChilliDB, then use that identifier when importing your data back in - this way ChilliDB will match the Id from your file with the record in ChilliDB already.