9,400
edits
Documents: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 84: | Line 84: | ||
[[File:Document location entity sync filter for sharepoint documents.png|600px]] | [[File:Document location entity sync filter for sharepoint documents.png|600px]] | ||
=== SharePoint integration details === | |||
=== SharePoint | |||
SharePoint is organized via sites and lists. Resco mobile apps synchronize with specific SharePoint lists - document libraries. | SharePoint is organized via sites and lists. Resco mobile apps synchronize with specific SharePoint lists - document libraries. | ||
| Line 110: | Line 98: | ||
Resco mobile apps sync first these two above-mentioned entities (as part of the standard sync) and then use them to control communication with SharePoint. | Resco mobile apps sync first these two above-mentioned entities (as part of the standard sync) and then use them to control communication with SharePoint. | ||
Make sure that these entities exist and are enabled in your backend. In the case of Salesforce, the backend admin probably needs to create them manually. Then you can enable the entities in your app project in Woodford. At the minimum, the sharepointsite table must have a single record pointing to a suitable SharePoint site; document locations are created by Resco apps when needed. | |||
Resco apps support 3 alternative ways of SharePoint communication: | Resco apps support 3 alternative ways of SharePoint communication: | ||
| Line 116: | Line 104: | ||
* Enable the '''SharePoint REST API''' configuration setting to use ListService partially using REST API. This interface is more efficient than the first because it does not need GetList API calls. | * Enable the '''SharePoint REST API''' configuration setting to use ListService partially using REST API. This interface is more efficient than the first because it does not need GetList API calls. | ||
* Enable '''New SharePoint REST API''' configuration setting to use the full REST API. It is just as efficient at the second option. Additionally, it uses the OAuth authorization, with a single sign-on with Dynamics possible. | * Enable '''New SharePoint REST API''' configuration setting to use the full REST API. It is just as efficient at the second option. Additionally, it uses the OAuth authorization, with a single sign-on with Dynamics possible. | ||
=== Resco Cloud === | |||
To enable SharePoint in Resco Cloud, proceed as follows: | |||
In the [[Admin Console]]: | |||
# Select '''Data > Manage Data''' from the menu. | |||
# Go to the '''SharePoint Site''' entity and click '''New''' to create a new record. | |||
#* Click '''Show System Fields''' to access all fields for the record. | |||
#* Enter the '''Name''' and the '''Absolute URL''' parameter, then click '''Save'''.<br>[[File:Sharepoint site record.png|300px]] | |||
# Go to the '''Document Location''' entity and click '''New''' to create a new record. | |||
TBD | |||
== External document synchronization filter options == | |||
[[Document filters]] available in the [[Configuration]] section of Woodford allow you to exclude specific documents from download to the Mobile CRM app’s database, based on the file type, entity, a file they’re associated to, how many and what maximum size per file type, etc. | |||
See also this [https://youtu.be/iLZ43KxGEW0?t=44m18s part] of our webinar. {{Badge|Webinar}} | |||
== Technical information == | |||
On the device, external documents are stored in two locations: | |||
* Document headers are stored in the database entity resco_sharepointdoc. Each record describes one document - its file name, path, size... but mainly the lookup to the owning CRM record (resco_regardingid). | |||
* Document bodies are stored separately in the blob storage. | |||
=== Document synchronization === | === Document synchronization === | ||