topic Re: Max size for Parameter schema in a callable recipe[SOLVED] in Workato Pros Discussion Board

Max size for Parameter schema in a callable recipe[SOLVED]

samuel-malaga — Fri, 12 Aug 2022 21:38:30 GMT

I've been trying create a parameter schema in a callable recipe using a Json and im always getting the following error: Invalid schema(found fields with invalid type/name) but the message is kind of odd because this schema is used in another recipe i developed in workato and in said recipe the schema is valid, could it be the size of it that is triggering this error? There is specific information about the limits of a json schema for a callable recipe parameter schema?

Ps: The schema contains 400 fields, i already tried to update the scema by json(same error) and by uploading a file(file too big error)

Re: Max size for Parameter schema in a callable recipe[SOLVED]

gary1 — Sat, 13 Aug 2022 01:52:23 GMT

Are you able to share the schema or link to it? You can use pastebin.com to quickly make a link to share text.

Re: Max size for Parameter schema in a callable recipe[SOLVED]

samuel-malaga — Sat, 13 Aug 2022 02:02:37 GMT

Here is the schema file already in Json. This was extracted from workato itself

Re: Max size for Parameter schema in a callable recipe[SOLVED]

samuel-malaga — Sat, 13 Aug 2022 02:04:52 GMT

Or the link here: https://pastebin.com/uC8xQXDR

Re: Max size for Parameter schema in a callable recipe[SOLVED]

gary1 — Sat, 13 Aug 2022 03:07:03 GMT

Thanks for sharing. The "name" key can't contain spaces.

If you try this, it will throw the error:

[

{

"control_type": "text",

"label": "Batch ID",

"type": "string",

"name": "Batch ID"

}

]

If you try this, it will work fine:

[

{

"control_type": "text",

"label": "Batch ID",

"type": "string",

"name": "Batch_ID"

}

]

Re: Max size for Parameter schema in a callable recipe[SOLVED]

gary1 — Sat, 13 Aug 2022 03:13:48 GMT

It's worth noting that when you use the CSV connector to generate the JSON schema using an existing header with spaces and irregular characters, it bypasses the check for spaces and irregular characters. This means that if you try to copy/paste the schema into another action (like a Collection), it won't work.

My fix for this is to update the source CSV header by find/replacing all spaces with underscores, and any other invalid characters, then doing the CSV header schema generation, and then finally copy/pasting the "good" JSON schema into the Collection.

This happened to me very recently, so I feel your pain : )