Changes

Jump to navigation Jump to search
420 bytes added ,  10:45, 29 July 2020
Line 227: Line 227:     
* '''Max Sync Records''': Maximum number of records per entity to download. This is a hard limit that violates data integrity. (More restrictive sync filter is a better way to reduce app data.) We recommend setting this parameter to a value that exceeds the maximum count of records in your largest entity.
 
* '''Max Sync Records''': Maximum number of records per entity to download. This is a hard limit that violates data integrity. (More restrictive sync filter is a better way to reduce app data.) We recommend setting this parameter to a value that exceeds the maximum count of records in your largest entity.
: This setting also applies to intersect (NN) entities, however, the limit is multiplied by 5. If some NN records are missing on the client, the consequence is that some records that are related on the server will be unrelated on the client.
+
: If a certain entity exceeds this threshold, it may also impact other entities:
 +
:* This setting also applies to intersect (NN) entities, however, the limit is multiplied by 5. If some NN records are missing on the client, the consequence is that some records that are related on the server will be unrelated on the client.
 +
:* Attachments related to non-downloaded records will be deleted in the sync cleanup phase.
 +
:* Child records of non-downloaded records will be deleted in the sync cleanup phase.
 +
:* If the entity B uses [[Sync Filter]] with an inner link to an entity with too many records,  some entity B records can be deleted in the sync cleanup phase.
    
* '''Max Attachment Size''': Max size of an attachment (documents, notes, email attachments) in bytes to be downloaded during sync. Larger attachments can be downloaded on user request.
 
* '''Max Attachment Size''': Max size of an attachment (documents, notes, email attachments) in bytes to be downloaded during sync. Larger attachments can be downloaded on user request.

Navigation menu