A newer version of this page is available. Switch to the current version.

PdfExportOptions.ExportEditingFieldsToAcroForms Property

Specifies whether to convert a report's editing fields to AcroForms on PDF export.

Namespace: DevExpress.XtraPrinting

Assembly: DevExpress.Printing.v18.2.Core.dll

Declaration

[DefaultValue(false)]
[TypeConverter(typeof(ExportEditingFieldsToAcroFormsConverter))]
[XtraSerializableProperty]
public bool ExportEditingFieldsToAcroForms { get; set; }
<DefaultValue(False)>
<TypeConverter(GetType(ExportEditingFieldsToAcroFormsConverter))>
<XtraSerializableProperty>
Public Property ExportEditingFieldsToAcroForms As Boolean

Property Value

Type Default Description
Boolean

false

true, to export report editing fields to PDF AcroForms; otherwise, false.

Property Paths

You can access this nested property as listed below:

Library Object Type Path to ExportEditingFieldsToAcroForms
Cross-Platform Class Library RemotePrintingSystem
.ExportOptions.Pdf.ExportEditingFieldsToAcroForms
ExportOptions
.Pdf.ExportEditingFieldsToAcroForms
PrintingSystemBase
.ExportOptions.Pdf.ExportEditingFieldsToAcroForms
WinForms Controls PrintingSystem
.ExportOptions.Pdf.ExportEditingFieldsToAcroForms
XtraSchedulerReport
.ExportOptions.Pdf.ExportEditingFieldsToAcroForms
WPF Controls ExportOptionsContainer
.Pdf.ExportEditingFieldsToAcroForms
PrintingSystem
.ExportOptions.Pdf.ExportEditingFieldsToAcroForms
PrintingSystem
.ExportOptions.Pdf.ExportEditingFieldsToAcroForms
Reporting XtraReport
.ExportOptions.Pdf.ExportEditingFieldsToAcroForms
DocumentOperationRequest
.ExportOptions.Pdf.ExportEditingFieldsToAcroForms

Remarks

When you export a report document to PDF, enable the ExportEditingFieldsToAcroForms property to generate a fillable PDF form (AcroForms). The fields that you make editable in Print Preview remain fillable in the resulting PDF document.

Specifics and Limitations

The following limitations apply to editing field export to PDF AcroForms:

  • Text Fields

    PDF AcroForms do not support a form content's vertical alignment.

    Single-line field text becomes center-aligned and multi-line text is top-aligned.

    Text becomes multi-line when it contains new line characters or when word wrap is specified in the field's format string.

  • Character Comb Fields

    The XRCharacterComb control's interactive content cannot be multi-line in the resulting PDF file.

    When this control displays text on multiple lines, it is converted to individual lines in PDF export.

  • Check Boxes

    A radio group is maintained in a PDF file only if it is contained on a single page.

    To make a radio group read-only, enable the radio group's first control's ReadOnly property. An individual check box cannot be made read-only if it participates in a radio group.

  • Drop-Down Lists

    Custom drop-down lists are available in Print Preview mode but are not exported to PDF.

Ediing field export to AcroForms is not supported in PDF/A-1b documents.

When you export text editing fields to PDF, fonts used to fill these fields are selected according to PDF export settings. However, non-embedded fonts are always used to populate these fields in the PDF viewer.

Field Name Generation Algorithm

Form field names are generated in the following way:

  • For regular fields, the name pattern is EditingField.ID_#. It consists of three parts: the EditingField.ID property value, an underscore sign, and an automatically incremented zero-based counter. If the EditingField.ID value is not provided, the "AcroFormField" literal is used instead.

    For instance, AcroFormField_0 (if EditingField.ID is empty) or label1_3 (if EditingField.ID is set to label1).

  • For group fields, the name pattern is RadioGroupAcroFormField_groupName, where RadioGroupAcroFormField is a hard-coded literal and groupName is the CheckEditingField.GroupID property value. For instance, RadioGroupAcroFormField_myGroup.
  • Multi-line Character Comb editors are split into distinct editors that follow the same name conversion.
See Also