熱門: 資料更新於2026年10月27日

軟體分類

網路軟體1,356
通訊社群321
影音軟體898
繪圖與影像539
辦公軟體1,124
開發工具3,134
AI工具529
安全與隱私385
系統工具3,114
遊戲523
教育與科學239
網路與IT284

Altova MapForce 2025 Basic Edition舊版本下載(所有版本)

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

這裡收錄Altova MapForce 2025 Basic Edition從2025年3月7日到目前2025.02.00.01的2個版本,每個版本都連到開發商的官方安裝檔。

2025: 2 2 25
版本日期大小檔案
2025.02.00.01最新版本 2025年5月17日 77.8 MB 32位元 EXE 76.1 MB32位元 EXE 76.0 MB32位元 EXE 74.9 MB32位元 EXE 76.6 MB32位元 EXE 77.8 MB
更新紀錄
[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 2025年3月7日 — 32位元 EXE32位元 EXE32位元 EXE32位元 EXE32位元 EXE
更新紀錄
[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