I più scaricati: Dati aggiornati al 27 ottobre 2026

Categorie

Internet1356
Comunicazione321
Audio e video898
Grafica e design539
Ufficio e produttività1124
Strumenti di sviluppo3134
Strumenti di IA529
Sicurezza e privacy385
Strumenti di sistema3114
Giochi523
Istruzione e scienza239
Rete e IT284

Altova MapForce 2025 Basic Edition: versioni precedenti da scaricare

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

Qui sono elencate 2 versioni di Altova MapForce 2025 Basic Edition, dalla prima (7 marzo 2025) fino all’attuale 2025.02.00.01. Ognuna rimanda ai file di installazione del produttore.

2025: 2 2 25
VersioneDataDimensioneFile
2025.02.00.01Ultima versione 17 maggio 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
Note di rilascio
[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 marzo 2025 — 32 bit EXE32 bit EXE32 bit EXE32 bit EXE32 bit EXE
Note di rilascio
[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