The SharePoint Content entity defines which lists, folders, and files will be displayed in a portal.

Fields

Field Field Requirement Description
Name Business Required The primary name for this content record.
Key Business Required

A unique key that will be used by the portal to define which SharePoint Content to render.

The Key may only be composed of alphanumeric characters (a-z, 0-9), hyphens (-), and/or underscores (_).

Document Locations Business Required

Defines which Document Location(s) will be viewable. The options are:

  • First or Default – Only files from the first-created document location will be viewable. Additional locations will not be selectable. If no locations exist, one will be created using the default values.
  • Default – Only files from the default document location will be viewable. Additional locations will not be selectable. If the default location does not already exist, it will be created. The default location is defined as the Document Location with a relative URL value that matches {displayname}_{id}.
  • All – All document locations associated to the currently viewed record will be viewable and selectable. Only currently existing locations will be included, and no new locations will be created.
  • Custom – Only document locations that match the associated Document Location Templates will be viewable and selectable. Any locations that do not exist yet will be created.
Entity Logical Name Business Required The Entity Logical Name for the entity to which this SharePoint Content will apply.
Subfolder Path None

v1.3.14+

A folder path underneath the document location from which files will be displayed/downloaded, and to which they will be uploaded.

Note: this field is only valid for the "First or Default" Document Location.

Metadata Mapping None

v1.4.2+

Defines the mappings between the entity named in Entity Logical Name and columns in SharePoint. See SharePoint Metadata Mapping for more details.

Note on Document Locations:

Only locations comparable to the default CRM folder structure are officially supported. In this scenario, a SharePoint Document Location record should refer to a folder on SharePoint, and have a Parent Site or Location that is another SharePoint Document Location referring to a list in SharePoint. This Parent Site or Location must have a Parent Site or Location that is a SharePoint Site:

 

For example:

 

Scenarios with more than two levels of SharePoint Document Locations are not supported:

 

However, any number of subfolders under a valid SharePoint Document Location are accessible:

 

Also, any number of SharePoint Site subsites are also supported:

 

Related Records

Entity Description
Document Location Templates

Defines which Document Location Templates will be evaluated when the SharePoint document list is rendered.

Only used when Document Locations is set to Custom.

Permissions

Defines which SharePoint Permissions will be applied when the SharePoint document list is rendered. Multiple permissions may be applied to a Content record, and permissions may be shared by multiple SharePoint Content records.

Only permissions whose Entity Logical Name value matches the content's Entity Logical Name value may be associated.