Working with gen1 and gen2 Printing Layouts: Limitations, Conversions, and Best Practices

Shortcut to the following sections in this article:

1. Legacy Templates vs. ArcGIS Pro-based Layouts
2. Conversion issues from VertiGIS Printing Designer to ArcGIS Pro Layouts
3. Conversion issues from ArcGIS Pro Layouts to VertiGIS Printing Designer
4. Printing Designer vs. ArcGIS Pro vs. VertiGIS Studio Desktop
5. Publishing or Updating ArcGIS Pro Layouts without VertiGIS Studio Desktop

Introduction

VertiGIS Studio Printing has evolved significantly from the gen1 (DevExpress‑based) printing templates to the gen2 (ArcGIS Pro–based) layout model. While most templates can be converted, there are important limitations and behaviors to be aware of when working with legacy templates.

This article explains what happens during conversion, how different editors (Printing Designer, ArcGIS Pro, VertiGIS Studio Desktop) compare, and which template elements are known to cause issues.
 

1. Legacy Templates vs. ArcGIS Pro–based Layouts

Gen1 templates were built using DevExpress technology. Gen2 layouts, in contrast, are based on ArcGIS Pro (.pagx) layouts. 

This means:

• A .pagx layout is not edited “natively” (when the web-based Printing Designer is used)

• The system internally translates the layout to DevExpress structures and back,

• Small differences or limitations may appear.

In short: Printing Designer does not offer the same range of functions as ArcGIS Pro, nor is this its intended purpose. Editing a .pagx layout in the Printing Designer will never be a 1:1 ArcGIS Pro editing experience. If you want to use the full capabilities of ArcGIS Pro, you need to create and edit your layouts directly in ArcGIS Pro.

2. Conversion issues from VertiGIS Printing Designer to ArcGIS Pro Layouts 

When converting templates between gen1 (DevExpress‑based) and gen2 (ArcGIS Pro‑based) layouts, some elements cannot be translated exactly. This happens when:

• Legacy DevExpress controls have no ArcGIS Pro equivalent,

• Certain layout properties exist in one editor but not the other, or

• The two engines simply render elements differently.

In these cases, unsupported elements are either:

• not mapped,

• skipped during conversion, or

• replaced with safe default values.

Whenever this occurs, the system writes a warning message to the browser console, helping users identify which parts of the layout were not successfully converted.

2.1 Unsupported or Hidden Controls (Skipped During Conversion)

The following gen1 controls have no gen2 equivalent. Therefore, they are ignored during conversion and will not appear in the print output. A console warning is generated for each unsupported control.

• Barcode (XRBarCode)
• Check Box (XRCheckBox)
• Rich Text (XRRichText)
• Character Comb (XRCharacterComb)
• Table elements (XRTable, XRTableCell, XRTableRow, XRCrossTableCell)
• Page Break (XRPageBreak)
• Cross‑band Line (XRCrossBandLine)
• Cross‑band Box (XRCrossBandBox)
• Image (only certain DevExpress‑specific image configurations)

2.2 Scripting Support Disabled

Scripting is a DevExpress-only feature and cannot be mapped to gen2. Therefore:

• The scripting toolbox is disabled
• All script-related properties are hidden
• Any existing script elements in a gen1 template are skipped

2.3 Hidden or Unsupported Properties for XRLabel

The following label properties are not supported in gen2 and are therefore not mapped:

• Text Format String (textFormatString)
• Background Color (backColor)
• Bookmark / Parent Bookmark
• Allow Markup Text (allowMarkupText)
• Text Trimming (textTrimming)
• Process Duplicates Modes / Targets
• Process Null Values
• Text Fit Mode (textFitMode)

If these properties exist in a gen1 template, they are ignored, and a warning appears in the console.

2.4 Unsupported PageInfo Formats

These PageInfo modes cannot be mapped to gen2 and will be skipped:

• Current of Total (NumberOfTotal)
• Page Number (Roman, lowercase)
• Page Number (Roman, uppercase)

Fallback: The system uses a supported default page numbering mode instead of Roman (lower- and uppercase) Page Number. A console warning will inform users of the change.

2.5 Unsupported Band Types

These DevExpress band types are not available in gen2 and therefore:

• are hidden in the editor,
• not mapped during conversion, and
• result in a warning in the console.

Unsupported band types include:

• Page Header / Footer
• Group Header / Footer
• Vertical Header / Detail / Total Bands
• Report Header / Footer
• Detail Report Band
• Sub‑Band

3. Conversion issues from ArcGIS Pro Layouts to VertiGIS Printing Designer

When ArcGIS Pro layouts are opened in the VertiGIS Studio Printing Designer, they must be converted into the DevExpress‑based layout model used by the Designer. Because the two layout engines support different structures, properties, and rendering behavior, certain ArcGIS Pro elements cannot be mapped exactly. As a result, some settings may be simplified, adjusted, or skipped during conversion.

Whenever possible, ArcGIS Pro-specific attributes from the .pagx are maintained, even when they cannot be rendered, typically because there is no such attribute displayed in the Printing Designer. However, when the element in question is changed in the Printing Designer, this hidden information is lost.

VertiGIS continuously improves the conversion process, and some issues will be fixed when technically possible. However, due to fundamental differences between ArcGIS Pro and the DevExpress engine, we cannot guarantee that all conversion issues can be resolved or that every layout will convert perfectly.

List of current known conversion issues (ArcGIS Pro --> VertiGIS Studio Printing Designer):

• Legend and scale bar font sizes behave incorrectly on large page sizes (e.g., A0).
• Scale line conversion unintentionally changes the Compute at Center option, which may cause export issues.
• Some controls added to a Blank Page template do not print at their intended size (e.g., Legend).
• Logo images may fail to print when using an Image URL in VertiGIS Studio Printing Designer.
• The sizing property of Image controls is not respected by the Printing Engine.
• Date formats in Dynamic Text may differ from Esri documentation.
• Page info elements are not shown correctly as layout fields in the print dialog.
• Parameter values may be unintentionally affected by the parameter title.
• Configurations of layout fields using a multi‑value function field may behave unexpectedly.
• Preserve scalebar settings adjusted in Pro may be changed when the layout is modified in the Printing Designer.
• Margins are ignored for layouts created via the Blank Page template.
• On Blank Page templates, many controls may be drawn with an unexpected solid black border.

List of conversion limitations:

• Expressions set on print element properties don't work.
• Support for configuration of PAGX-like properties for overview map frame.
• Certain Polygon graphics from Pro layouts are not converted correctly.
• Third‑level group layers do not work as expected.
• Dynamic field with layer credits from ArcGIS Pro layouts is not converted correctly, which may result in missing or incomplete credit text.
• A vertical alignment issue can also occur when elements have a rotation defined, causing the converted field to appear misaligned in the Printing Designer or printed output.
• Vertical scalebars

4. Printing Designer vs. ArcGIS Pro vs. VertiGIS Studio Desktop

Each editor has different capabilities and different internal behaviors. Switching between editors can lead to:

• Repeated conversions

• Element loss

• Layout adjustments or distortions

5. Publishing or Updating ArcGIS Pro Layouts without VertiGIS Studio Desktop

When a layout is created or edited directly in ArcGIS Pro, the following workflow ensures that the ArcGIS Pro configuration remains intact and that the layout is published correctly as a Portal Item.

1. Prepare or edit your layout in ArcGIS Pro.
   Make your changes in the .pagx file as usual.

2. Import the .pagx layout into the VertiGIS Studio Printing Designer.
   This step registers the layout with Printing and allows it to be used as a ArcGIS Pro layout in VertiGIS Studio Web.

3. Update the layout using ArcGIS Online / ArcGIS Enterprise

   • Open the item page of your existing layout template

   • Select Update Data

   • Upload the new or updated .pagx file

   • To avoid conversion issues, please keep using ArcGIS Pro to edit this layout instead of the VertiGIS Studio Printing Designer

The Portal Item will be overwritten with the updated file without breaking your ArcGIS Pro configuration.