Importing existing data from Collect to Collect Mobile

Dear Luka,
As you have understood correctly, the file containing the data in Collect Mobile is "nodes", that is a SQLite database.
Updating that file outside from Collect Mobile won't be easy, but I will try to explain the structure of it.
The table you will have to fill is ofc_view_model and these are the most relevant columns:

• id: internal identifier (a progressive number)
• relevant: 0 = not relevant, 1 = relevant (evaluated at runtime, according to the rule defined in the Survey Designer in Collect)
• status: OK - no errors in the attribute/entity/record, VALIDATION_ERROR - validation error found, EMPTY - the attribute/entity/record is empty
• parent_id: parent node internal id (the value of the ID column corresponding to the parent node); the parent node is the "entity" that contains the attribute or the entity defined in the row; the value can be "null" only for the root entity;
• parent_entity_id: equal to the column above but it has a value only when the node is a multiple attribute or a multiple entity
• definition_id: internal id of the "definition¨ of the node, as it is in the file idml.xml of the survey export generated by Collect;
• survey_id: it's always 1, because every survey has it's own nodes db;
• record_id: internal identifier of the record; every record will have a row in the nodes table that identifies it, with a null value in the parent_id column;
• record_collection_name: name of the root entity defined in the survey designer (e.g. cluster); it is filled only when the row corresponds to a record;
• record_key_attribute: it contains "1" only if the node corresponds to a key attribute of the record, 0 otherwise;
• node_type: type of node, following the type defined in the survey designer. 1=record (identifies the row corresponding to the entire record), 2=entity, 4=entity collection (list of entities), 5=attribute collection, 6=code, 7=coordinate, 8=date, 9=numeric (double), 12=file, 13=numeric (integer), 15=taxon, 16=text, 17=time
• val_*: the value columns (with val_ as prefix) are filled in depending on the type of attribute (e.g. val_text is for text attributes, val_date for date attriutes etc.)
• created_on and modified_on: timestamp with the creation and modified dates;

Hoping this is clear enough, we wish you the best luck updating this table by yourself!
Let us know if you need further assistance, many thanks,
Open Foris Team