9,310
edits
Synchronization steps: Difference between revisions
Jump to navigation
Jump to search
→SharePoint integration with Microsoft Dynamics
| Line 677: | Line 677: | ||
In standard integration, CRM admin selects entities (account, contact…) that can have SharePoint attachments. In turn, respective SharePoint document libraries are created: One library per one entity with the library names identical to the entity names. | In standard integration, CRM admin selects entities (account, contact…) that can have SharePoint attachments. In turn, respective SharePoint document libraries are created: One library per one entity with the library names identical to the entity names. | ||
Formally, the Dynamics server contains | Formally, the Dynamics server contains multiple entities that describe the locations of SharePoint documents that are managed by Dynamics CRM: | ||
* sharepointsite entity records describe SharePoint sites. | * '''sharepointsite''' entity records describe SharePoint sites. | ||
* sharepointdocumentlocation records (“locations”) contain a URL (subfolder of some SharePoint document library) and a reference to the CRM record (regardingobjectid) to which the documents are attached. | * '''sharepointdocumentlocation''' records (“locations”) contain a URL (subfolder of some SharePoint document library) and a reference to the CRM record (regardingobjectid) to which the documents are attached. | ||
* '''sharepointdocument''' entity: From Resco CRM point of view, this entity contains redundant information; do not use it in your projects. | |||
<syntaxhighlight lang="sql"> | <syntaxhighlight lang="sql"> | ||