Pivot table pdf nightmare

Former Member
Former Member $organization

Hi Forum,

My question is on emailing and downloading pdfs with pivot tables from dashboards.  If a dashboard includes a pivot table, not all columns or rows are shown in the PDF or email. They become cut off.

Unfortunately the pivot table is needed. It is the best way to show all the information for a specific audience. 

We can manually create a pdf with all columns if we download from a widget, but we want this to be automated and emailed, which you can not do from a widget.

Is there anything we can do? We have tried changing the PDF to A3, extending rows to 200,  

We are on Tessitura Analytics version 15.0.3

Thank you,

Siorna and the Ticketing team!!! 

Parents
  • Former Member
    Former Member $organization

    Hi Sarah and Michael, 

    Thank you so much for your suggestions. We've nearly got it to work for the columns with these tips and your absolutely right, if we break the rows out into multiple widgets more PDF pages appear so we can schedule. That's great to know. 

    Unfortunately the report we were hoping to schedule is our sales by performance report, for all productions on sale. This is usually a tess report that we were hoping to replace with analytics dashboard. The workaround of creating widgets for all the individual productions is way too manual, instead of an automated filter on one widget by date.

    Does anyone know why the PDF dashboard cant be configured to show all rows in a pivot widget? 

    Thanks again for all your support!

    Siorna  

  • Hi Folks --

    We just ran into this same limitation.  We took the same approach as everyone on this thread -- manually paginating a single Pivot Table widget using multiple widgets in a dashboard -- but made it more sustainable with a little customization magic and the use of the ORDERING() function.  We added a custom Cube Table to the Seats and Tickets Cube that ranks the Production Season of each Performance in our database by date of the first Performance in the Production Season.  We then use the Sisense ORDERING() function to dynamically re-rank all rows, which we can then use as a filter for each widget in the dashboard.  We display 20 rows per widget.  If anyone changes the date range in the dashboard filter, it automatically paginates the results.

    Happy to discuss this our approach in greater detail!

    DGomez

Reply
  • Hi Folks --

    We just ran into this same limitation.  We took the same approach as everyone on this thread -- manually paginating a single Pivot Table widget using multiple widgets in a dashboard -- but made it more sustainable with a little customization magic and the use of the ORDERING() function.  We added a custom Cube Table to the Seats and Tickets Cube that ranks the Production Season of each Performance in our database by date of the first Performance in the Production Season.  We then use the Sisense ORDERING() function to dynamically re-rank all rows, which we can then use as a filter for each widget in the dashboard.  We display 20 rows per widget.  If anyone changes the date range in the dashboard filter, it automatically paginates the results.

    Happy to discuss this our approach in greater detail!

    DGomez

Children
No Data