‘Improved large query performance’ EAP & Dashboards | Community
Skip to main content

‘Improved large query performance’ EAP & Dashboards

  • January 12, 2022
  • 3 replies
  • 0 views
Mihail11

Hello,

The above EAP is enabled on our sandbox instance and I've performed some tests. I was advised by support to post one of the findings here and seek advise:

Is it expected that I am able to avail of the 500,000 rows export only via the query builder and not via a dashboard? I placed a test query on a dashboard and set the default time range to something which would cause it to fail loading due to result size (“Results are too large to load”) but I would have expected to still receive the full result (under 500,000 rows) if I schedule the dash to deliver via e-mail. Instead I am only receiving an empty Excel file (claiming to be corrupted, mind you).

      3 replies

      Brett13
      • Brett13
      • Community Manager
      • January 13, 2022

      Hey Mihail,

      That doesn't sound like expected behavior so I'm going to create a ticket on your behalf to see if our Customer Care team can dig into this for you.

      You'll receive an email shortly stating your ticket has been created.

      Cheers!

      M
      • Mihail12
      • January 31, 2022

      Hi Zendesk Team,

      As advised by Support I'm adding another post here to officialize my feedback:

      While testing the large query export it became evident that the feature only applies to exports made via the query builder. This leaves a gap when it comes to non-admin reporting users who have to rely on the dashboards and the drill-in. 

      Further improvements in this area would be much appreciated.

      Cheers!

       

        Jahn11
        • Jahn11
        • June 22, 2022

        Same issue for me. I have signed up for Large EAP queries to get the extracted report (less than 500k rows) in one go but no success.

        Zendesk team is still asking me to splice the data per month which defeats the purpose of having this feature. 

        Please provide fix for this one the SOONEST possible.

        Terms & ConditionsCookie settingsAccessibility statement