9,400
edits
Documents: Difference between revisions
Jump to navigation
Jump to search
→Enterprise-level document storage considerations
| Line 220: | Line 220: | ||
Resco mobile platform natively supports integration with various [[Documents|cloud-based services]]. The users of [[Resco mobile apps]] can attach blobs to records, but behind the scenes, documents are not stored in CRM but in the cloud service. It is important to note that it is the mobile app that provides the experience of meshing CRM data with cloud blobs, and there is no explicit linking between records and blobs in CRM. Resco uses a predefined folder structure to store blobs in cloud services and uses a naming convention to locate the files (with SharePoint, you have some more control over blob locations). | Resco mobile platform natively supports integration with various [[Documents|cloud-based services]]. The users of [[Resco mobile apps]] can attach blobs to records, but behind the scenes, documents are not stored in CRM but in the cloud service. It is important to note that it is the mobile app that provides the experience of meshing CRM data with cloud blobs, and there is no explicit linking between records and blobs in CRM. Resco uses a predefined folder structure to store blobs in cloud services and uses a naming convention to locate the files (with SharePoint, you have some more control over blob locations). | ||
With this approach, you can take advantage of an optimized sync engine and [[document filters]], but on the other hand, it is not possible to finetune sync to such an extent (e.g., no links to other tables in [[Sync_Filter|sync filters]]). Also, web-based Resco tools (e.g. questionnaire player in browser) don’t support cloud documents. There are some more [[Documents#Troubleshooting|limitations]] and [[Documents#Caveats|caveats]], most notably that cloud documents require parent records to be in the offline database to function properly. So to sum it up, this is what we would recommend as a very robust and convenient option in case you don’t need your blobs in CRM and | With this approach, you can take advantage of an optimized sync engine and [[document filters]], but on the other hand, it is not possible to finetune sync to such an extent (e.g., no links to other tables in [[Sync_Filter|sync filters]]). Also, web-based Resco tools (e.g., questionnaire player in browser) don’t support cloud documents. There are some more [[Documents#Troubleshooting|limitations]] and [[Documents#Caveats|caveats]], most notably that cloud documents require parent records to be in the offline database to function properly. So to sum it up, this is what we would recommend as a very robust and convenient option in case you don’t need your blobs in CRM and accept the other limitations mentioned above. | ||
;Outlook for 2023 and beyond | ;Outlook for 2023 and beyond | ||
Since 2019, Microsoft's preferred way of storing blobs in Dataverse and CRM Online is File/Image columns. Behind the scenes (although the curtain is rather thin), these are stored in Azure Storage and count against File capacity. Since [[Releases/Spring_2023|release 16.0]], Resco offers basic support of the [[Dynamics#File_columns|File column]] (read-only mode on entity forms, manual download+cache). Contact your business development manager at Resco if you're interested in learning about (and shaping!)Resco's plans in this area. | Since 2019, Microsoft's preferred way of storing blobs in Dataverse and CRM Online is File/Image columns. Behind the scenes (although the curtain is rather thin), these are stored in Azure Storage and count against File capacity. Since [[Releases/Spring_2023|release 16.0]], Resco offers basic support of the [[Dynamics#File_columns|File column]] (read-only mode on entity forms, manual download+cache). Contact your business development manager at Resco if you're interested in learning about (and shaping!) Resco's plans in this area. | ||
;Disclaimers: | ;Disclaimers: | ||