Example: Configure frontend paging and filtering
In case you display related data on the frontend via widgets inheriting ContentView, for example, NewsView, you can configure the widgets to use paging, filtering, or sorting.
The following code example demonstrates how you can enable paging for related News items:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
<sf:newsview controldefinitionname="NewsFrontend" runat="server" title="Related news" urlkeyprefix="" contentviewdisplaymode="Master"> |
|
|
|
<RelatedDataDefinition RelatedFieldName="R_Dynamic_News" RelatedItemType="Telerik.Sitefinity.DynamicTypes.Model.Pressreleases.PressRelease" RelationTypeToDisplay="Child" RelatedItemSource="DataItemContainer"> |
|
</RelatedDataDefinition> |
|
|
|
<ControlDefinition ControlDefinitionName="NewsFrontend" runat="server" ProviderName="newsProvider3"> |
|
<Views> |
|
<sf:ContentViewMasterDefinition ViewName="NewsFrontendList" AllowPaging="true" ItemsPerPage="2" runat="server"> |
|
</sf:ContentViewMasterDefinition > |
|
|
|
<sf:ContentViewDetailDefinition ViewName="NewsFrontendDetails" runat="server"> |
|
</sf:ContentViewDetailDefinition > |
|
</Views> |
|
</ControlDefinition> |
|
|
|
</sf:newsview> |
In addition, you can set filter and sort expressions using the relevant properties of the MasterDefinition – FilterExpression=’Title.Contains(“jQuery”)’ and SortExpression="Title desc"