Graphical tools in MapForce make it easy to define data mapping and processing rules for converting JSON. With support for JSON as both an input and output format, MapForce can be applied in countless ways, including these common scenarios:
| JSON ↔ XML | Often needed when integrating modern web APIs (JSON) with legacy enterprise systems |
| JSON ↔ databases | Inserting JSON data into relational database tables or extracting relational data to generate JSON for APIs |
| JSON ↔ Excel or CSV | For integration with business tools and reporting systems, or preparing data for data warehouses and analytics platforms |
| JSON ↔ EDI | For integrating traditional B2B systems with modern applications |
| PDF ↔ JSON | Extract data from PDFs and convert to JSON for integration with APIs or other systems |
| Parsing API responses | Mapping JSON returned by REST APIs into usable internal formats (e.g., DB records or XML structures) |
When you need to map JSON data but don't have a schema corresponding to a JSON or JSON5 instance, MapForce will infer one for fast mapping according to the document structure.
Once your JSON mapping project is defined, you can click Output to transform the data instantly. (For mapping JSON to a database, the Output view shows the SQL statements that will be executed against the database once the mapping is initiated.)
For advanced troubleshooting, MapForce includes an interactive data mapping debugger for tracing how data flows through source and target nodes during mapping execution.
To automate recurrent JSON conversion projects, you can deploy your MapForce projects to MapForce Server. MapForce Server provides high-performance automation of any-to-any data mapping projects at a fraction of the cost of legacy and big-iron data management products.
