Skip to main content

DevExpress v24.2 Update — Your Feedback Matters

Our What's New in v24.2 webpage includes product-specific surveys. Your response to our survey questions will help us measure product satisfaction for features released in this major update and help us refine our plans for our next major release.

Take the survey Not interested

XtraReport.VerticalContentSplitting Property

Gets or sets a value indicating whether report controls outside the right page margin should be split across pages, or moved in their entirety to the next page.

Namespace: DevExpress.XtraReports.UI

Assembly: DevExpress.XtraReports.v24.2.dll

NuGet Package: DevExpress.Reporting.Core

#Declaration

[DefaultValue(VerticalContentSplitting.Exact)]
[SRCategory(ReportStringId.CatBehavior)]
public VerticalContentSplitting VerticalContentSplitting { get; set; }

#Property Value

Type Default Description
VerticalContentSplitting Exact

A VerticalContentSplitting enumeration value, which specifies the splitting method of report controls in the vertical direction.

Available values:

Name Description
Exact

When the brick dimensions do not fit into the right page margin, the rest of the brick content is split across two pages.

Smart

When the brick dimensions do not fit into the right page margin, the brick content is moved to a new page in its entirety.

#Remarks

If a report control is printed outside the right page margin, you have two alternative options:

The VerticalContentSplitting setting is specified for the entire report; it cannot be set for individual controls or bands.

#Tips and Limitations

#Smart Split Specifics

In a scenario where the label spans the entire page width within PageHeaderBand, the reporting engine treats the right side of the label as the border for content splitting. In this case, both the Smart and Exact settings will result in the same behavior.

To address this situation, move the header label to TopMarginBand, and it will not be treated as part of the content to be separated based on the right margin. This approach allows the report engine to correctly handle content splitting based on the actual content within the DetailBand.

See Also