The CMSRepeater control displays a list of formatted document data.

  • Provides a built-in data source for loading Kentico documents. You do not need to write code for retrieving and binding the data.
  • Supports Kentico transformations.
  • Supports nested controls (See Using nested controls).

Inherits from: BasicRepeater
Web part equivalent (portal engine): Repeater

Getting started

The following tutorial shows how to display a list of news items (CMS.News documents) using the CMSRepeater control:

  1. Create a new Web form in your web project.
  2. Drag the CMSRepeater control from the toolbox onto the form.
  3. Set the following properties for the control:

    • Path: /News/%
    • ClassNames:
    • OrderBy: NewsReleaseDate DESC
    • TransformationName:
    • SelectedItemTransformationName:
    <cms:CMSRepeater ID="CMSRepeater1" runat="server" Path="/News/%" ClassNames="" OrderBy="NewsReleaseDate DESC" TransformationName="" SelectedItemTransformationName="" />
  4. Save the web form.
  5. Right-click the web form in the Solution explorer and select View in Browser.

The resulting page displays a list of news items.



You can set the following properties for the CMSRepeater control:

CMSRepeater properties


Sample value


Name of the transformation applied to alternating items.

Enter the transformation name in format <document type code name>.<transformation name>.



Indicates whether the control automatically performs data binding during the Init event. (Inherited from BasicRepeater)



Allows you to access the object of the data source control.



ID of the data source control.



Indicates whether the control loads data during the Load event instead of the default Init event.



Indicates whether the built-in DataPager control is used to page the list.

If you wish to use a UniPager, set this property to false and add a separate UniPager control to the page.



Indicates whether the control should be hidden when no data is loaded. The default value is False. (Inherited from BasicRepeater)



HTML code rendered as a separator between the displayed items.



Enter the IDs of any nested controls (CMSRepeater, CMSDataList...), separated by semicolons.



Gets or sets the pager data item object. (Inherited from BasicRepeater)



If set, the pager does not modify the DataSet containing paged items, but the pager itself behaves as if the amount of paged items were identical to this value.

The value must be set to -1 for the property to be disabled.

(Inherited from BasicRepeater)



Sets the number of displayed items per page.



Can be used to set or get the pager control and its properties.



Custom data connected to the object. (Inherited from BasicRepeater)



Name of the transformation applied to the selected item.

Enter the transformation name in format <document type code name>.<transformation name>.



Indicates if the control renders edit and delete buttons next to the displayed documents in editing modes (Page tab in the Pages application and On-site editing mode).



Name of the transformation applied to standard items.

Enter the transformation name in format <document type code name>.<transformation name>.



Text shown when the control is hidden by the HideControlForZeroRows property. (Inherited from BasicRepeater)

"No records found."

Document filtering properties


Sample value


Indicates if the control checks the permissions of the user viewing the page. If the value is false (default value) no permissions are checked.

If true, the control only loads documents for which the user viewing the page has read permissions.



Specifies which document types the control loads and displays. Identify document types through their code names, separated by semicolons (;).

You can use the * wildcard as a substitute for any number of characters. For example Product.* includes the document types Product.Camera, Product.CellPhone, Product.Computer etc.

If the property is left empty, the control retrieves all document types by default. In the case of menu and navigation controls, only page (CMS.MenuItem) documents are loaded by default.

Note: If the control loads all document types (empty value), only the common data columns from the View_CMS_Tree_Joined view are available in the retrieved data. The specific fields of individual document types are not included. You need to keep this in mind when writing the code of transformations, WHERE conditions, ORDER BY expressions etc.



Indicates whether the control loads documents from the website's default culture version if the required documents are not available in the user's selected culture.

Only applies if you do not set the TreeProvider property manually.



Specifies the culture code of the documents that the control loads. If not specified, the control automatically uses the preferred culture of the user viewing the page.



Allows you to manually assign a DataSet or DataTable containing the documents that the control displays. You do not need to set this property for standard scenarios.



Indicates if the control filters out duplicated (linked) documents from the data.



Specifies the maximum number of content tree sub-levels from which the control displays documents. This number is relative, i.e. counted from the location of the page where the control is placed, not from the root of the website.

Enter -1 to load all child documents.



Path of the documents that the control loads.

See: Writing document path expressions



If enabled, the control only loads published documents.



Gets or sets the TreeProvider object used by the control to access document data. If you do not assign a TreeProvider object, the control automatically creates a new instance.


Document relationship properties


Sample value


If set, the control only loads documents that are related to the document with the specified NodeGUID. You can find the Node GUID of documents on the Properties -> General tab in the Pages application.

Enter "11111111-1111-1111-1111-111111111111" to dynamically load documents related to the current document.



Determines whether the document specified through the RelationshipWithNodeGUID property is on the left or right side of the relationship.

  • If true, the control displays documents on the right side of the relationship.
  • If false, the control displays documents on the left side of the relationship.



Specifies the type of the document relationship. Enter the code name of the relationship.


CMS Base control properties


Sample value


List of the cache keys on which the control's cached data depends. When the specified cache items change, the control clears its cache.

Each item (dependency) must be on one line.

If you leave this property empty, the control uses default dependencies.

See also: Setting cache dependencies, Configuring caching



Sets the name of the cache key used to store the control's content. If you leave the value empty, the system generates a default name containing variables, such as the control ID, the selected culture and the name of the user who loaded the page.

The system cache is shared by all pages in your application, so cache item names representing different data must be unique globally. If you have multiple controls that load the same data, you can share the cache keys between the controls (optimizes loading of content and avoids redundant data in the cache).

If the content displayed by the control depends on variables, such as URL parameters, you can set a custom name dynamically in the page's code behind.

See also: Caching the data of page components, Configuring caching

"CMSRepeaterNews" +


Sets the number of minutes for which the control caches content retrieved from the database.

  • 0 indicates that control does not cache content
  • -1 indicates that the control uses the site-level content caching settings

Allows you to set up caching of content so that the control doesn't have to retrieve content from the database on each request.

The caching mechanism uses absolute expiration time. This means that cache items expire after a specified time period even if the page containing the control wasn't requested.

See also: Caching the data of page components, Configuring caching



Gets or sets the filter control used to limit the data read by the control.



Gets or sets the code name of the filter control used to limit the data read by this control.



Gets or sets the ORDER BY clause of the SQL query that the control uses to load data.

"NewsReleaseDate DESC"


Database table columns that the control loads for documents, separated by commas ( , ). If null or empty, the control loads all available columns.



Specifies the code name of the Kentico website for which the control loads data.



If true, the control stops all processing — does not load or display any data or other HTML output.



Specifies the maximum number of database records that the control loads.



Gets or sets the WHERE clause of the SQL query that the control uses to loads data.

"ProductPrice > 100"

Note: The CMSRepeater is derived from the ASP.NET Repeater control, so you can also set any of the base properties.

Appearance and styling

You can modify the appearance of the CMSRepeater control by setting the standard properties available for the ASP.NET Repeater control (inherited through the BasicRepeater).

The design of the items in the list is determined by the transformations specified through the AlternatingTransformationName, TransformationName and SelectedItemTransformationName properties, or by the code of item templates.