Changing the Mapping Settings Print this Topic Previous Page Up One Level Next page

Home >  Common Tasks > Working with Mappings >

Changing the Mapping Settings

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 or the Java, C# or C++ application name for the generated transformation files.

Base Package Name

Defines the base package name for the Java output.

Make paths absolute in generated code

Defines whether the file paths should be relative or absolute in the generated program code, as well as in MapForce Server Execution files (mfx) and in mapping functions deployed to FlowForce Server. For more information, see About Paths in Generated Code.

Ensure Windows path convention for file path

The "Ensure Windows path convention...." check box makes sure that Windows path conventions are followed. When outputting XSLT2 (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.

Line ends

This combo box allows you to specify the line endings of the output files. "Platform default" is the specific default for the target operating system, e.g. Windows (CR+LF), macOS (LF), or Linux (LF). You can also select a specific line ending manually. The settings you select here are crucial when you deploy a mapping to FlowForce Server running on a different operating system.

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.

© 2019 Altova GmbH