Supported Sources and Targets
When you change the transformation language of a MapForce mapping, certain features may not be supported for that specific language. The following table summarizes the compatibility of mapping formats and transformation languages in MapForce Enterprise Edition.
Remarks:
•Built-in means that you can execute the mapping by clicking the Output pane in MapForce or run it with MapForce Server.
Mapping format | XSLT 1.0 | XSLT 2.0 | XSLT 3.0 | XQuery | C++ | C# | Java | BUILT-IN | |
|---|---|---|---|---|---|---|---|---|---|
XML1 |  | | | | | | | | |
CSV and text | | | | | |||||
Text, via MapForce FlexText | | | | | |||||
JSON | | | | ||||||
XBRL2 | | | | | |||||
Excel 2007 and later3 | As data source | | | | | | |||
As data target (generate new file) | | | | ||||||
As data target (update existing file) | | ||||||||
EDI | ASC X12 | | | | | ||||
HIPAA X12 | | | | | |||||
HL7 version 2 | | | | | |||||
HL7 version 3 | | | | | | | | | |
IATA PADIS | | | | | |||||
NCPDP SCRIPT EDIFACT format | | | | | |||||
NCPDP SCRIPT XML format | | | | | | | | | |
SAP IDoc | | | | | |||||
SWIFT MT | | ||||||||
SWIFT MX / ISO 20022 | | | | | | | | | |
TRADACOMS | | | | | |||||
UN/EDIFACT | | | | | |||||
Databases4 | ADO | | | | |||||
ADO.NET | | | |||||||
JDBC | | | |||||||
Native SQLite | | ||||||||
Native PostgreSQL | | ||||||||
ODBC | | | | | |||||
Web Services5 | REST-Style | | |||||||
SOAP | | | | ||||||
Protocol Buffers | | ||||||||
Raw binary files | | ||||||||
Footnotes:
1.XML with digital signatures processing is supported only in BUILT-IN.
2.XBRL with digital signatures processing is supported only in BUILT-IN.
3.This refers to Excel 2007 or later files in Office Open XML format (.xlsx). Note that the Strict Open XML Spreadsheet format also uses the .xlsx extension but is supported only as a data source (not as a data target). For more information, see Microsoft OOXML Excel 2007+.
4.Limitations apply depending on the database type and the target environment. For more information, see Database mappings in various execution environments.
5.This refers to calling Web Services, not generating them from mappings. For SOAP Web Services, note that client certificates, preemptive authentication and WS-Security are not supported in the generated C# and Java code. For more information, see Calling Web Services.