9,334
edits
Storage analyzer: Difference between revisions
Jump to navigation
Jump to search
→SharePoint
| Line 373: | Line 373: | ||
(Tip: These records increase sync overhead. Remove them via better SyncFilter.) | (Tip: These records increase sync overhead. Remove them via better SyncFilter.) | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Explanation: | |||
* Every CRM entity using SharePoint documents needs to have defined so-called root location. | |||
* Every CRM record with SharePoint documents has one or more locations, where documents are stored on SharePoint. | |||
* FullSync queries SharePoint in batches of 100 locations/call. A high number of locations means, a) many server requests, and b) potentially too many files downloaded. The case shown in the example looks like overkill, hence the warning. | |||
* Unknown locations point either to entities not included in the customization or to records that were not downloaded to the client, i.e. excluded by the sync filter. The recommendation (tip) says that the sync filter for sharepointdocumentlocation entity should be adjusted to the customization to avoid unnecessary sync overhead. | |||
[[Category:Support]] | [[Category:Support]] | ||