Respect Widget Script when exporting to csv!

Comments

3 comments

  • Avatar
    Moti Granovsky

    Hi Ian,

    Unfortunately widget scripts can't be applied to the CSV export, as that happens on the server - when a widget is exported to CSV, the widget's query is re-run against the Elasticube with a different format setting. 

    Generally, widget scripts are meant for visual manipulations (and not so much for data transformation) and CSV exports are intended to retrieve the "raw" data behind a widget. 

    However, it is possible that you could substitute your widget script with a different query structure, which would mean you'd get the same outcome with CSV exports - could you post an example of the data you're retrieving from the Elasticube and what it looks like after the script has transformed it? Perhaps there's a way to achieve the same result without a script.

    Thanks!

    1
    Comment actions Permalink
  • Avatar
    Ian Emmons

    Hey Moti,

    Given this data:

    I'm looking to produce this output:

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    Hi Ian,

    I've been trying to come up with a creative solution for this but haven't found one so far (was mostly looking to see if this can be done as a custom table in the Elasticube).

    There is no way to make CSV exports "respect" the widget script, for the reasons I've explained above.

    The only other direction I can think of is a server-side interceptor for the export endpoint, which would apply this logic to the CSV payload before passing on the response. This is something Sisense Professional Services may be able to assist you with - you can reach out to your CSM to set up a meeting with them.

    0
    Comment actions Permalink

Please sign in to leave a comment.