We’d like to be able to upload a .json file using the Tulip File Input widget (or suggest a different widget). Looks like this file type is not currently supported. Any possibility this can be expanded?
Hi @akbeta thanks for the request! We can certainly take a look at this and see what we can do.
1 Like
Hi @shep,
we would also like the ability to store additional file extensions in the File Input, File Variable, and the table field type File.
Currently, it looks like this when you try it with other files such as .eml, .cad, .json:
With additional extensions, we could, for example, manage more files related to manufacturing orders in Tulip.
It would be best to have a whitelisting page in the settings where we can enable additional file extensions ourselves.
Thanks
Jeremy
1 Like
Hi @Jeremy thanks for this. I’ve relayed this to the appropriate team internally and will see what we can do!
1 Like
I am surprised by this limitation, as you could easily just change the file extension to .txt and upload it as is? Tulip does not have any relevant functionality for actually using JSON files. Although I am sure they had a reason.
Hey @akbeta, quick question regarding .json files — what exactly would you be doing with the json files after uploaded via the File input widget? I’m guessing they would be stored in a table, but then what would you do with them thereafter?
Hi @shep, we would be processing the JSON via our internally-developed middleware. We’ve developed software to take an exported Tulip JSON and run audits on it to ensure our apps are being developed under internally-defined rules. The ability for our citizen developers to upload a JSON directly into a Tulip App, then run a connector function to tell our middleware to analyze that JSON would significantly reduce the number of errors we encounter.
At the end of the day, is there a reason why these filetypes aren’t supported for upload? What we do with the files shouldn’t really be relevant.