โ08-12-2022 02:38 PM
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)
โ08-12-2022 08:13 PM
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 : )