Transactions Using XML Import Rules

14 Transactions Using XML Import Rules

When using an XML import rule to load a transaction’s data, sections that are set as “Can Grow” (dynamic), but also specifying a non-custom paper-size (e.g. Letter, Legal, A4, etc. ) may now result in change if the section contains any multiline text (MLT) fields.

Combining the Can Grow and Shrink attribute with a fixed (non-custom) paper size is not permitted in the standard DMStudio managed documents. However, if the original form was imported from a legacy (form.dat) style resource definition, it is possible the conflicting attributes might have been defined manually.

The xml import rule was changing the size of the section if the dynamic option was specified, with the theory being that reformatting a text area or MLT that expands could “grow” the section. Since a fixed paper size section cannot technically grow, this causes a formatting conflict and unnecessary pages may get created.

If this impacts your regressions, there are few possible methods to correct.

If you do not expect to use custom size sections on import, you could try to specify this INI option and see if the problem is resolved.
```
<XMLIMPORT>  
DontResizeImages=Yes
```
This is a legacy option that when included tells the XML import rule to not change dynamic size sections.

If you do have some sections that should be dynamic and some that should not be, this solution will not be your choice.
Alternatively, you could remove the dynamic option from the section within the form. As mentioned, DMStudio does not let you manage this combination of options, therefore to change the option manually requires checking the form out of the library and then manually editing. Look for your section name and just below it will be a DAPOPTIONS node with a VALUE attribute.
```
<SECTION NAME="mysection"> 
<DAPOPTIONS VALUE="DW#100600"/> 
```
It is important that you only remove the W in this value and do not change any of the other characters.

Once done, save the file and check the form back into the library from DM Studio as a new revision. Subsequent runs will no longer have the problem.
As a final possible solution, you could specify the DAPOPTIONS node in your import XML. This too requires the manual step of first checking the form out the library to see what DAPOPTIONS VALUE is specified for your section. Copy that setting, omitting the W as indicated in the previous option.

Changing in this manner will only impact those transactions using this particular input file. Any other transaction files you use would have to be modified similarly.