Beliebt: Daten aktualisiert am 27. Oktober 2026

Kategorien

Internet1.356
Kommunikation321
Audio & Video898
Grafik & Design539
Büro & Produktivität1.124
Entwicklertools3.134
KI-Tools529
Sicherheit & Datenschutz385
Systemtools3.114
Spiele523
Bildung & Wissenschaft239
Netzwerk & IT284

Altova MapForce 2025 Basic Edition: alte Versionen herunterladen

Graphical data mapping tool for any-to-any data conversion, data integration, & ETL

Hier sind 2 Versionen von Altova MapForce 2025 Basic Edition aufgeführt, von 7. März 2025 bis zur aktuellen 2025.02.00.01. Jede verweist auf die Installationsdateien des Herstellers.

2025: 2 2 25
VersionDatumGrößeDateien
2025.02.00.01Aktuell 17. Mai 2025 77,8 MB 32-Bit EXE 76,1 MB32-Bit EXE 76,0 MB32-Bit EXE 74,9 MB32-Bit EXE 76,6 MB32-Bit EXE 77,8 MB
Versionshinweise
[Webservices] Provide support for GraphQL
[Code Generation] Validation of customer mapping takes considerably longer (& output preview results in XSLT error) in v2021r3 than in v2019
[Database functionality] Describe circumstances under which the shared database connection option is unavailable
[IDE GUI] Inserting a processing instruction before the root element defeats the 'Prefix for target namespace' setting
[PDF Extractor] PDF Extractor fails to capture text from customer PDF
[Excel file functionality] Inaccurate "Cannot find the file" error shown when passing a non-XSLX file to a XSLX component
[XSLT2 Engine] Generated XSLT2 from MF 2025 is roughly 30 times larger in size than that generated by MF 2019 - file specific
[Localization] The menu text in the Japanese version of MapForce has largely reverted to English
2025.00.00.01 7. März 2025 — 32-Bit EXE32-Bit EXE32-Bit EXE32-Bit EXE32-Bit EXE
Versionshinweise
[Code Generation] namespace declarations on the root element can be invalid against a DTD with namespaces
[EDI-X12-HL7] Ambiguous segments in config warning message should state where a required file is missing
[Database functionality] Add support for Azure Cosmos NoSQL database
[Webservices] Please mention that the web service is called for each conditional HTTP response that has been configured
[Code Generation] Don't add namespace declarations to root element for elements which are unused in the output instance
[Nonexistent feature] Serializing XML to string does not add DOCTYPE declaration
[Database functionality] Checking the 'Use object names relative to default schema' setting with an MS Access DB results in unexpected behaviour in conjunction with Global Resources