If you choose to change database fields from the default database, there are several considerations to keep in mind. It is essential to ensure that any modifications do not interrupt data flow from Connect or lead to unexpected data loss.
On this page you have the following options::
Database name
When the default database has been created, it is possible to rename the Database in Copernica. Changing the database name does not affect the existing fields or data.
Adding database fields
New fields and areas of interest can be added through the Copernica interface. Since Connect does not fill these fields unless you set up rules to fill them, make sure that they are not required for profile creation. Otherwise, profiles might fail to be created through Connect if mandatory fields are left empty.
Name of field
When adding a field, use a custom name with a prefix or suffix unique to your account (for example, Custom_Fieldname instead of Fieldname). Connect periodically updates the default database with new fields. If the names overlap, Connect overwrites the data. By using custom prefixes or suffixes, the chance of collisions is minimised.
Removing database fields
It is possible to remove existing fields from the current database. However, some fields propagate data back to Connect (for example, opt-in fields). Once a field is removed, any data for that field will no longer be saved in Copernica. Recreating a field with the same name allows new data to be saved again from that moment onward. There is no option to restore previously lost data retroactively.
Changing database fields
When changing properties of existing database fields, consider whether the change alters the type of input the field can process. If data received from Connect no longer matches the expected format, it will not be saved.
Changing field type
The field type in Copernica determines the kind of input that can be processed. Changing fields that can process any input (Text or Long text) to those that accept limited input (Number or Multiple choice) is not recommended. When Copernica cannot process the incoming data from Connect, the field remains empty without triggering an error message. It is recommended to only change limited input fields to Text if more flexibility is needed, so no data will be lost.
Changing field options
Removing field options from the default database (for instance, removing the Other option from the gender field) does not stop Connect from sending that value. Data that does not match the available options in Copernica will not be saved, and no error is returned to Connect. If new options are added in Copernica, the same options must be added to the rules in Connect. Otherwise, Connect will not propagate data for those new options. To see which options are by default available, check the default database setup for Copernica.
Changing field name
Changing field names in the default database is not recommended because Connect matches fields based on name. Changing a name can lead to data loss if Connect can no longer identify the field. A possible workaround is using Database follow-ups to fill a custom field, while hiding the original field from the database overview.