Global setting validation in a replicated environment
To prevent issues, certain database settings must be used consistently in environments that use either database replication, or database subsetting. When you are working in replicated environments, you are notified if these settings are not consistent, and must resolve the issue before the database can be used.
About this task
| iBase setting | Description |
|---|---|
| Audit level | The amount of information that is stored about user interactions with the data that is stored in your system. As different audit levels record different amounts of information, it is impossible to synchronize data in environments where the audit levels differ. |
| Audit history | The types of interaction that are recorded in the audit logs. As different audit history settings record different types of information, it is impossible to synchronize data in environments where the audit history is different. |
| Field attachments | Whether documents and images can be associated with specific fields rather than stored in
fields that are set up as document or image field types. To prevent these attachments from
potentially being lost, you cannot synchronize databases unless their field attachment setting
matches. Note: You can use field attachments to change how entities are displayed on charts based on
the information of interest. This information is accessible when the record is open, but is not
searchable.
For more information about field attachments, see Enabling field attachments. |
| Field security | Whether you can set the SCC access to a record at a field level. To prevent information
from potentially being visible when it should be restricted, you cannot synchronize databases unless
their field security setting matches. For more information about the field security, see Enabling field security. |
| Field confidence | Whether you can grade the information in a record at a field level. To prevent this grading
information from potentially being lost, you cannot synchronize databases unless their field
confidence setting matches. For more information about field confidence, see Enabling field confidence. |
| Soft delete | Soft delete allows records to be removed from view without removing their details from the
database. For more information about the soft deleting, see Enabling soft delete. Note: Soft delete has to be enabled in replicated databases. |