Hi team - two quick questions: 1. When exporting a visualization or table to XLSX, is there a way to have the "Keep attribute cells merged" defaulted to off (screenshot attached)? 2. When exporting an entire dashboard to PDF, is there a way to include the filters that are applied to the export? If not, could this be passed along as an improvement request? Or just the general ability to configure the PDF export options of an entire dashboard to include or exclude certain visualizations or rich text, etc.

Hi Brett again, Thank you for contacting us 🙂 I am happy to help. 1. Could you please let me know your use case? While we cannot change that option by default, it may be possible to achieve this through (probably) a hard coding and the use of the API. However, for each export action, you'll need to obtain the "executionResult" from the dev console or create it using the following payload: https://www.gooddata.com/docs/cloud/api-and-sdk/api/api_reference_all/#operation/createTabularExport, You can then explicitly change the parameter "mergeHeaders" from true to false. The response should look something like this:

{
  "exportResult": "string"
}

And this exportResult string, you have to add it in this GET call endpoint

api/v1/actions/workspaces/{workspaceId}/export/tabular/{exportId}

Whenever you make changes to the visualisation, you will need to retrieve another 'exportResult'. Therefore, the process is more complicated than just making two clicks. 2. Unfortunately, it is currently not possible to view the applied filters in the exported PDF dashboard. I will definitely submit a product feedback request on your behalf. Please let us know if you need any further assistance.

Hi Mauricio, thank you for getting back to me. Appreciate you adding the improvement request for the 2nd item. Appreciate your recommendations for the first item as well. The use case we have here is that a lot of our end users are using table exports for reporting capabilities where they want to use filters, but the merged cells are not allowing and they are overlooking unchecking this and then reaching out to our helpdesk as to why filters are not working as expected. We do educate our end users via a KB article calling this out, but not everyone uses them and thought it might just be easier to have the default unchecked

🎉 New note created.