SharePoint for Connect 365 allows Microsoft Dynamics 365 administrators to configure SharePoint lists for display in Microsoft Dynamics 365 portals. This feature can be configured to support:
The interface displayed in the portal is a listing of SharePoint files associated to the currently viewed Dynamics 365 record.
Files can be uploaded by dragging a file or files directly into the upload area, or by clicking the upload area and selecting a file or files.
Multiple files may be queued for upload and paused or cancelled while in progress.
Files can be downloaded from SharePoint to the local computer by clicking the file name hyperlink.
Files can be deleted by clicking the trash can icon.
Using liquid web templates, the SharePoint files can be displayed anywhere that liquid code can be used, including web pages, web forms, and entity forms.
The primary configuration entity used for selecting which files to surface in the portal is the SharePoint Content entity. Any SharePoint enabled entity within Dynamics 365 can be surfaced in the portal.
Dynamics 365 records can have one or more document locations. Through the use of the Document Locations field, the exact set of document locations can be selected for display in the portal.
Access to the SharePoint files are defined through a declarative permissions data model.
This page will provide step-by-step instructions for getting started with SharePoint for Connect 365.
The SharePoint Content entity defines which lists, folders, and files will be displayed in a portal.
The SharePoint Content entity defines which lists, folders, and files will be displayed in a portal.
The SharePoint Permission entity defines which actions will be allowed when a SharePoint Content record is rendered.
The SharePoint Metadata Mapping entity defines how field values from a CRM record, as well as from the logged-in portal user's Contact and Parent Account, can be saved to an uploaded SharePoint document.
Connect 365 Settings control how the Connect 365 application interacts with its features, including SharePoint.
In this scenario, we will expose a set of documents for a product record to be downloadable by the general public with no authentication or user account required.
In this scenario, we will allow a portal user to download, upload, and delete documents to and from their own profile.
In this scenario, we will allow portal users to download documents for support cases related to their company from any document location in the CRM.
In this scenario, we will create two different subfolders under a single document location.
