Any plans on allowing binary uploads to the import and attachment functions?

Options

It seems like the API is geared towards a desktop application with constant user interaction. In my case, I am using it to generate some reports for my company and pushing them out to a specified folder. Currently, to generate the report, I am aggregating the majority of the data into a DataSheet, and converting it to a SpreadSheet, (.xlsx,) but with the API, I have to parse through it to create a sheet. The XLSX import function is looking for a string file and path, but my API is running in a docker image, so I am not saving anything locally. It would be great to be able to upload a byte[] or stream, instead of pointing to a string path. Does anyone know a way to get around it?

Best Answer

Answers