Developer
XML and XSLT Integration
Zynk's XML and XSLT integration works on XML once it exists. It reshapes documents with XSLT stylesheets, splits large files into batches, merges many files into one, loops through records and turns XML into CSV. Integration teams use it between the systems they connect, such as Sage, ERP platforms, SQL Server databases and SFTP sites, to fit data to each target's layout.
Capabilities may differ depending on the product.
Benefits
Why businesses connect XML and XSLT
Stylesheets do the reshaping
The XSLT Transform task applies an XSLT 1.0 stylesheet to an XML file. Parameters such as a company name can be passed in at run time, so one stylesheet can serve several companies or trading partners.
Large files in manageable batches
XML Split breaks a big file into smaller ones using an XPath query and a record limit per file, so a large export can be imported a few hundred records at a time. XML Split and Repeat can also group records by a value, such as a branch.
Loop through every record
XML Repeater and XML Split and Repeat run a set of sub-tasks for each record or file, for example posting one document per customer or sending one file per supplier, without building a separate workflow for each.
Decisions based on content
If XML Contains checks a file for a value before the workflow carries on. XML Select stores a value, a count or a total in a workflow variable, ready for later tasks to use in file names, filters or reports.
Many files merged into one
XML Merge and List and Merge XML Files combine many small files, such as one order per file dropped in a folder, into a single document that the target system can import in one pass.
CSV when a system needs it
XML To CSV produces a flat file for systems and people that still work with spreadsheets, such as a bank upload portal or a checking report for the finance team.
Capabilities
What you can do with XML and XSLT
Every task the Zynk XML and XSLT connector can run, grouped by the direction data moves.
Actions in XML and XSLT
Tasks Zynk can automate in XML and XSLT
9 tasks
- If XML contains → in XML and XSLT
- List and merge XML files → in XML and XSLT
- XML merge → in XML and XSLT
- XML repeater → in XML and XSLT
- XML select → in XML and XSLT
- XML split → in XML and XSLT
- XML split and repeat → in XML and XSLT
- XML to CSV → in XML and XSLT
- XSLT transform → in XML and XSLT
Need something that isn't listed?
Most XML and XSLT projects include at least one custom step. Our team builds it for you.
The problem
Why integrate XML and XSLT?
Two systems can both speak XML and still not understand each other. Element names differ, records are nested differently and one system wants a single file where the other sends hundreds. Without a transformation step, those gaps get closed with one-off code that is hard to test and harder to hand over.
Without integration
- Hand-written code for every change of XML layout
- Imports struggling with exports of many thousands of records
- Hundreds of single-order files processed one at a time
- Every step running even when a file holds nothing useful
- Data copied out of XML into spreadsheets by hand
With Zynk
- One XSLT stylesheet per layout, kept with the workflow
- Large files split into batches of a size you set
- Files merged into one document before import
- If XML Contains decides whether the rest of the workflow runs
- XML converts to CSV as part of the run
How it works
How the XML and XSLT integration works
Step 1: Receive the XML
XML arrives from an earlier task in the workflow: a connector export, a database query, a file collected from SFTP or the output of the XML connector's CSV, JSON or EDIFACT conversion.
Step 2: Shape it
XSLT stylesheets rename, filter and restructure elements to match the target's layout. Split, merge and select tasks set the batch size and pick out the values later steps need.
Step 3: Act on each part
Repeaters run sub-tasks once per record or file, and conditional checks skip files that are empty or irrelevant, so each import only receives data it can accept.
Step 4: Deliver
The finished XML goes to the target connector for import, or becomes a CSV for a system that needs a flat file. Split files can be kept, archived or deleted after processing, as you choose.
Integrations
What can you connect to XML and XSLT?
Example use cases for XML and XSLT integration
XML and XSLT and CSV
Turn finished XML into CSV for systems that only accept flat files, such as bank portals, older line-of-business tools or a spreadsheet your finance team checks.
XML and XSLT and SQL Server
Run a SQL Server query that returns XML, then use a stylesheet to shape the results for import into an accounting or ERP system.
XML and XSLT and SFTP
Collect XML files from an SFTP folder, merge or split them into the right batches, transform them and upload the result for the receiving system to pick up.
XML and XSLT integration FAQs
What is XSLT used for?
Which version of XSLT does Zynk support?
How do I split a large XML file in Zynk?
Can Zynk merge several XML files into one?
Can I convert XML to CSV?
How is this different from the XML connector?
Do I need to know XSLT to use Zynk?
See what Zynk can automate for your XML and XSLT setup
Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.
Book a callSee pricing →