I’d like to access the data that is saved by export_data_table within the Python workspace without having to write this out to a file and then read it back in, if possible. Has anyone else done this to offer suggestions? I’ve tried utilizing StringIO but get “TypeError: bad argument type for built-in operation”. I also wondered if I could make an adjusted version of the export_data_table function but don’t see/understand the specifics of what is happening in ExportDataTableCsv/ExportDataTableCsvRequest/ExportDataTableCsvReply.
@mstachur My apologies for the really late reply! We’ve had a few folks out of office during the past week, and your message unfortunately came in at roughly around that time. We’ve been catching up on things here and just came across your question.
In short, our Automation API does not provide a function to immediately read out decoded data from the capture. The main way we provide access to decoded data is via exporting it first as you’ve mentioned.
We’re tracking a feature request linked below to allow decoded data from the in-app terminal to be streamed to an external file. This is not exactly the functionality you need, but we could perhaps extend this to (1) the Automation API and (2) simply allow that data to be readable rather than streamed to an external file.
@timreyes Thanks for your response. Functionality to “(2) simply allow that data to be readable rather than streamed to an external file” would be great for our current need. I just added a vote and comment onto that feature request.
1 Like