Documents: Difference between revisions

Jump to navigation Jump to search
No change in size ,  17 August 2020
Line 109: Line 109:
=== Caveats ===
=== Caveats ===


Documents may consume large portion of device memory. Tips:
Documents may consume a large portion of device memory.
* Use MaxAttachmentSize setting or BlobStoreFilter to limit needed storage.
* Use MaxAttachmentSize setting or BlobStoreFilter to limit needed storage.
* To measure the used document storage (need to be done on Windows) go to the [[Log_files#Finding_physical_files_in_Windows_versions_of_mobile_apps|%APP_DATA% folder]], then subfolder blob, then subfolder resco_sharepointdoc.
* To measure the used document storage (need to be done on Windows) go to the [[Log_files#Finding_physical_files_in_Windows_versions_of_mobile_apps|%APP_DATA% folder]], then subfolder blob, then subfolder resco_sharepointdoc.
Line 119: Line 119:
Dynamics SharePoint integration
Dynamics SharePoint integration
* Dynamics lately added another SP-related entity: sharepointdocument - used internally by Dynamics for presentation purposes.
* Dynamics lately added another SP-related entity: sharepointdocument - used internally by Dynamics for presentation purposes.
Woodford admins might be tempted to enable this entity, but this would be pure overhead - Resco apps do not use it.
: Woodford admins might be tempted to enable this entity, but this would be pure overhead - Resco apps do not use it.
(Moreover, for MCRM versions prior to v12.2 this entity causes sync failure. (Because it does not have the rowversion field.))
: (Moreover, for MCRM versions prior to v12.2 this entity causes sync failure. (Because it does not have the rowversion field.))


Too many GetList calls
Too many GetList calls
Line 126: Line 126:


Root document locations
Root document locations
* Document locations are hierarchical. Resco apps require that you have a root location for each entity type which allows SharePoint attachments. For example, you need to have a location for "accounts". If there's such a location, MCRM can create location for any particular account record. It does so by creating a subfolder with the name <record_name>_<record_id>.
* Document locations are hierarchical. Resco apps require that you have a root location for each entity type which allows SharePoint attachments. For example, you need to have a location for "accounts". If the location exists, MCRM can create a location for any particular account record. It does so by creating a subfolder with the name <record_name>_<record_id>.
In the opposite case, Resco Mobile CRM refuses to create SharePoint attachments for the account entity.
: In the opposite case, Resco Mobile CRM refuses to create SharePoint attachments for the account entity.


== Additional resources ==
== Additional resources ==

Navigation menu