London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
This document describes how to configure Push to CMS functionality. The Push to CMS functionality allows transferring and keeping in sync SharePoint content with EPiServer CMS. In general there are two types of content available in SharePoint: Lists and Libraries. Those two types often match with two types of content in EPiServer CMS: Pages and Files. So SharePoint List items can be exported to EPiServer CMS as Pages and SharePoint Library items can be exported as Files. Some SharePoint Libraries can also be exported as EPiServer CMS Pages. Content from SharePoint is transferred to EPiServer CMS using Content Channel Web Services.
Create and make sure that the Content Channel exists and is correctly configured on the EPiServer CMS website as follows:
In order to enable connection from SharePoint to EPiServer CMS a web services access need to be configured as described in the Installation instructions.
Importing SharePoint Items
Ensure that field names of SharePoint items, to be exported, are properly mapped to the property names of the selected page type for each EPiServer CMS Content Channel. Note! Don't forget to create a mapping in the EPiServer Content Channel for the EPiServer PageName property. If no mappings are created, then EPiServer import only properties which names match to the properties of the page type being used.
Configure SharePoint website as follows:
The EPiServer CMS Content Channel configuration consists of the following parameters:
Special columns can be added to SharePoint lists and libraries in order to control the Push to CMS behavior. The columns should have names exactly matching to the names specified below. For now there are two columns supported:
"Send to EPiServer" - this column should have a "Yes/No" type. Only those items that have "Yes" value set in this column will be sent to EPiServer CMS. If an item was previously sent to EPiServer CMS and then the value of the column is changed to "No" - the item will be deleted from EPiServer CMS.
"EPiServer Page Type Name" - this column should be of any string type: "Single line of text", "Choice" or "Calculated" and so on. A value specified in this column is a name of EPiServer CMS Page Type. When an item is exported to EPiServer CMS as a page, the specified page type will be used for a newly imported page. The page type should also have a mapping in the Content Channel settings.
Document last saved: February 27, 2013