Please enable JavaScript to view this site.

Altova MapForce 2020 Basic Edition

You can change the document-specific settings of the currently active mapping design file from the Mapping Settings dialog box. This information is stored in the *.mfd file.

To open the Mapping Settings dialog box:

On the File menu, click Mapping Settings.


Mapping Settings dialog box

The available settings are as follows.


Application Name

Defines the XSLT1.0/2.0 file name prefix for the generated transformation files.

Make paths absolute in generated code

This check box affects all paths in mapping components, except paths to external library files (such as XSLT libraries).


The check box defines whether the file paths should be relative or absolute in the generated program code. See also Paths in Various Execution Environments.

Reference libraries with paths relative to the generated XSLT / XQuery files

This check box is applicable when the mapping language is either XSLT or XQuery*.


This option is typically useful if your mapping references an XSLT or XQuery library, and you plan to generate XSLT or XQuery files from the mapping. If you want the library paths to be relative to the directory of the generated XSLT or XQuery code, select the check box.

If the check box is not selected, the library paths will be absolute in the generated XSLT or XQuery code. See also Library paths in generated code.

Ensure Windows path convention for file path

This check box is applicable when the mapping language is either XSLT 2.0 or XQuery*.


The check box makes sure that Windows path conventions are followed. When outputting XSLT 2.0 (and XQuery), the currently processed file name is internally retrieved using the document-uri function, which returns a path in the form file:// URI for local files.


When this check box is active, a file:// URI path specification is automatically converted to a complete Windows file path (e.g. "C:\...") to simplify further processing.

XML Schema Version

Lets you define the XML schema version used in the mapping file. You can define if you always want to load the schemas conforming to version 1.0 or 1.1. Note that not all version 1.1 specific features are currently supported.


If the xs:schema vc:minVersion="1.1" declaration is present, then version 1.1 will be used; if not, version 1.0 will be used.


If the XSD document has no vc:minVersion attribute or the value of the vc:minVersion attribute is other than 1.0 or 1.1, then XSD 1.0 will be the default mode.


Note:Do not confuse the vc:minVersion attribute with the xsd:version attribute. The former holds the XSD version number, while the latter holds the document version number.


Changing this setting in an existing mapping causes a reloading of all schemas of the selected XML schema version, and might also change its validity.


* Requires MapForce Professional or Enterprise Edition

© 2020 Altova GmbH