Oblíbené: Data aktualizována: 27. října 2026

Kategorie

Internet1 356
Komunikace321
Audio a video898
Grafika a design539
Kancelář a produktivita1 124
Vývoj3 134
Umělá inteligence529
Zabezpečení385
Systémové nástroje3 114
Hry523
Vzdělávání a věda239
Síť a IT284

Altova MapForce 2025 Basic Edition: starší verze ke stažení

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

Seznam obsahuje 2 verze programu Altova MapForce 2025 Basic Edition – od 7. března 2025 po aktuální verzi 2025.02.00.01. Každá verze vede na instalátory ze serveru výrobce.

2025: 2 2 25
VerzeDatumVelikostSoubory
2025.02.00.01Nejnovější 17. května 2025 77,8 MB 32bit EXE 76,1 MB32bit EXE 76,0 MB32bit EXE 74,9 MB32bit EXE 76,6 MB32bit EXE 77,8 MB
Seznam změn
[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. března 2025 — 32bit EXE32bit EXE32bit EXE32bit EXE32bit EXE
Seznam změn
[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