JSON / JArray Conversion Activities

Bronze Certified

Custom Activity

9 reviews

7.2k

Version: 1.1.0 (View History)

Overview

Reviews

Questions

Summary

A pack of 3 activities which can handle any nested and complex Json / JArray and converts it into XML, CSV files and Data Table.

Overview

The package contains 3 custom activities for conversion of JSON/JArray to other data formats:
1. JSON/JArray to CSV file.
2. JSON/JArray to XML file.
3. JSON/JArray to Data Table.
These activities accept all types of complex and nested JSONs either in a text file (specified in the input property InputJsonFilePath) with valid JSON/ JArray in it or it accepts JSON/Jarray string directly (specified in the input property InputJsonString) and creates an output CSV file or XML file, at user's designated path (specified in the input property OutputCSV/XMLFilepath) , or generates a DataTable from the input Json.
Json to CSV: To view the data in tabular format, output CSV file can be opened using Excel. The first row in Excel will be the headers, generated from all the tag names in JSON file. In case of multi-level nested JSON, it retains the complete path of each element, separated by slash '/'. (as explained in image Explanation 1.)
Json To XML: This activity converts Json/Array in XML format without any data loss. In case of JArray, element tags are added for each array element and in case of non-array objects Json keys are converted to XML tags and Json values are converted to XML inner text. Output of this activity should be .xml file. (as explained in image Explanation 3)
Json To DataTable: It converts input Json/JArray to Datatable and provides the flexibility of directly applying all Data Table functions like filtering the JSON Data. In case of JArray, each Data row is converted to Excel Row Item and in case of non JArray structure, all the tags generate headers and in case of multi-level nested JSON, it retains the complete path of each element, separated by slash '/' so as to prevent any data loss. (as explained in image Explanation 2)
Time taken for this conversion is proportional to the level of nested data structure of JSON (between milliseconds to few seconds).