CSV ActionHandler converts an existing CSV file from the HIRO Graph (blob on ogit/Attachment) to a proper JSON formatted table, represented by an ogit/Document/Spreadsheet. In this guide we will walk through the process from adding an attachment to Quering the JSON formated table created by CSV ActionHandler.
\nAuthenticate and retrieve a Graph Authentication token. Please refer to our documentation on HIRO Graph Auth API.
\nId for the 'data-scope' (environment) you want to interact with. This value will be written to the ogit/_scope attribute. If omitted the default scope of your account will be used. Please be aware, that this may lead to confusion if your account has access to multiple scopes. Therefore, it’s highly recommended defining your desired scope.
\nHaving a CSV file as an attachment in the HIRO graph. Please see below to create an attachment vertex and load the CSV data.
\nIn case you do not have an attachment vertex in the graph yet, a simple curl command is given below. Please refer to HIRO Graph REST API to know more about the API. In the following command replace <TOKEN> and <SCOPE_ID>. In this document we run our requests against the stage graph, replace the url with https://core.engine.datagroup.de/ for global graph. When a valid scope and token is used, you are presented with a response. Make a note of \"ogit\\/_id\", this will be used in the steps to follow.
\ncurl -k --request POST --url https://eu-stagegraph.almato.ai/api/graph/7.1/new/ogit%2fAttachment --header 'Authorization: Bearer $TOKEN' --header 'Content-Type: application/json' --data '{\"/name\": \"CSV\", \"ogit/_scope\": \"<SCOPE_ID>\"}'In this section we load the CSV data into the attachment created in the previous section. In the following curl command replace <ID> with \"ogit\\/_id\" from the previous step. The response is the contentId of the attachment. Please note, maximum size of csv file should not be bigger than maximum size of the vertex.
\ncurl --request POST --url https://eu-stagegraph.almato.ai/api/graph/7.1/<ID>/content --header 'Authorization: Bearer $TOKEN' --header 'Content-Type: text/csv'\n--data 'h1,h2,h3,h4\n> 1,2,3,5\n> 6,7,8,9\n> 10,11,12,13'The table given below consists of parameters that can be used in the KI to achieve the desired structure of JSON.
\n| Parameter | \nDescription | \n
|---|---|
keys (optional) | \nIdentifier if keys are represented by rows or columns, default being row. Expected values: row or column. | \n
colOffset (optional) | \nOffset rows of the table. Entries before the offset are ignored. Default: 0 | \n
rowOffset (optional) | \nOffset columns of the table. Entries before the offset are ignored. Default: 0 | \n
delimiter (optional) | \nDelimiting character. Default:, or Comma | \n
In the following KI example, we use the default parameter values. When an issue with variable ConvertToSpreadsheet and SourceId is created, this KI is triggered and the corresponding CSV is converted to JSON.
on\n ogit/_id\nwhen\n ConvertToSpreadsheet\n SourceId\ndo\n code: LOCAL::STATUS,\n body: LOCAL::RESULT = action(\n capability: \"CSVtoSpreadsheet\",\n sourceId: SourceId\n )\n if LOCAL::STATUS == \"200\" then\n log(\"SUCCESS: Your CSV is has been formated ${LOCAL::RESULT#result}\")\n TargetId = \"${LOCAL::RESULT#result['target_id']}\"\n\tdelete(ConvertToSpreadsheet)\n else\n log(\"ERROR ${LOCAL::STATUS}: ${LOCAL::RESULT}\")\n endlog SUCCESS: Your CSV is has been formated {\"target_id\": \"${TARGET_ID}\"}\nYou can modify the KI to use column as identifier:
\ndo\n code: LOCAL::STATUS,\n body: LOCAL::RESULT = action(\n capability: \"CSVtoSpreadsheet\",\n sourceId: SourceId,\n keys: \"column\",\n )\n
On successful execution of the KI, you were presented with the TARGET_ID which holds the ogit/_id of the created ogit/Documents/Spreadsheet node.\nThis node holds the JSON fomated CSV.
\n Row \n | \n\n Column \n | \n
\n \n \n | \n\n \n \n | \n