JSON is a lightweight data-interchange format. This connector transforms input JSON format to another data-interchange format XML (Extensible Markup Language), which is the standardized language similar to HTML in which data can be also stored, searched or exchanged with other systems.
Example
Following example shows how JSON is transformed to XML, element attributes can be specified by prefix @. Result XML is in Root element because XML needs to have root element to be well-formed.
Input data JSON (ver. 1.0.0)
JSON: JSON |
|---|
{
"@Id": 1,
"Email": "james@example.com",
"Active": true,
"CreatedDate": "2013-01-20T00: 00: 00Z",
"Roles": [
"User",
"Admin"
],
"Team": {
"@Id": 2,
"Name": "Software Developers",
"Description": "Creators of fine software."
}
}
Output data Text (ver. 1.0.0)
Text: String |
|---|
<?xml version="1.0" encoding="UTF-8"?>
<Root Id="1">
<Email>james@example.com</Email>
<Active>true</Active>
<CreatedDate>2013-01-20T00:00:00Z</CreatedDate>
<Roles>User</Roles>
<Roles>Admin</Roles>
<Team Id="2">
<Name>Software Developers</Name>
<Description>Creators of fine software.</Description>
</Team>
</Root>
Input & Output Schema
Input
JSON (ver. 1.0.0)
| Column | Data type | Allow null | Description |
|---|---|---|---|
| JSON | JSON | No | Input/Output in JSON format |
Output
Text 1.0.0
XML as plain text.
Text (ver. 1.0.0)
| Column | Data type | Allow null | Description |
|---|---|---|---|
| Text | String | No | Converted plain text. |
Release notes
3.0.4
- Plugin binaries update as a result of included connector change.
3.0.3
- Fixed shared nuget package versions.
3.0.2
- Fixed right processing of nullable properties.