Skip to main content
vigneshkumarr0001
June 18, 2025
Question

Issue in Plugin: JSON Tools Smart Services Load JSON to a database

  • June 18, 2025
  • 5 replies
  • 0 views

Hi everyone,

I'm trying to load json to db using this Appian smart serivces. My sample json data i have given below. It has multiple dynamics parameter for example user have multiple types of phone number. if it flattens json file then its working without any issue but sub paramters are not working as expected. Added more details below

Main Issue while accessing the json sub parameters which is dynamic

In smart service Load JSON to a database, "JSON key/Column Name mapping" Field for json fields key i have tried like this Phone.number as well as Phone[].number but while executing Process model considered as "FirstName", "Phone" as column instead of each table column fields like FirstName, PhoneType PhoneNumber. I cant able to navigate inside of sub paramters while mapping json key to table columns name

Plugin name: JSON Tools

Smart service name: Load JSON to a database

my sample appian rule

{
"FirstName": "First_Name",
"Phone[].number": """Phone_Number""",

}

and

{
"FirstName": "First_Name",
"Phone.number": """Phone_Number""",

}

Sample JSON:

{
  "FirstName": "Fred",
  "Phone": [
    {
      "type": "home",
      "number": "0203 544 1234"
    },
    {
      "type": "office",
      "number": "01962 001234"
    },
    {
      "type": "office",
      "number": "01962 001235"
    },
    {
      "type": "mobile",
      "number": "077 7700 1234"
    }
  ]
  }

5 replies

vigneshkumarr0001
June 19, 2025

while debugging JSON Tools plugin seem this plugin consider FirstName and Phone as table name. i dont know why "Load JSON to a database" alone Appian written like this but Schema validations using "Validate a JSON against a schema" working correctly even dynamic parameters. Hard to debug since there was no proper documentations in plugin and even plugin provided images are having outdated parameters. Anyone faced this issue and is there any way to overcome this?

davidj137213
June 19, 2025

I would suggest implementing a new process to format the JSON into a record or another structure with the required format. After that, use 'Write Records' or 'Write to Data Store Entity' to persist the information

vigneshkumarr0001
June 19, 2025

yes i too thought same but in this issue its a kind of stagging table, just to load large no of columns temporarily around 100+ columns