Important announcement: Upcoming changes to the Explore dashboard builders

Return to top

39 Comments

  • Terry Knox

    So, to clarify, within 8-12 months, every dashboard that we currently use will need to be re-built? Is that correct? They won't be transitioned over to the new builder, even in some sort of ugly version? 

    20
  • Tobias Hermanns

    We missing a lot of things in the new builder:

    - Bookmarks
    - Multiple Tab Support (Color etc.)
    - "Per Viewer" didn´t support Omni Channel Dataset
    - Some Querys on the dashboard can´t update or should not update if i.e. a Group is changed, in Classic Dashboard you can freeze it.
    - Export Limitations
    - E-Mail and Scheduling Limitations
    - Linking of dataset to each other Filter (we don´t want see 4x Assignee)

    Is there a list of features which will for sure not come from Classic and face out?

    19
  • 蘇詩婷

    Please provide a tool to easily migrate current dashboards to the new dashboard.
    And please make all the features that were available before available on the new dashboard.
    Will Zendesk be responsible for the labor and cost of manually rebuilding each and every one of the large number of existing dashboards?
    Please reconsider.

    17
  • Sydney Neubauer
    Zendesk Luminary

    Is this the announcement that is published that gives us over a year or will there be a more formal one that offers the tools and solutions to transfer over existing reports into the new builder? We would like exact timelines please

    15
  • Rafael Santos
    User Group Leader

    View-only access should be kept for longer unless there are easy migration tools for older dashboards.

    Due to Explore not having an Import/Export functionality, building some dashboards would take multiple days, which is quite expensive. And we have many huge ones.

    If we're forced to consider applying all that effort, the next best decision is to spend that time migrating all our Zendesk-based reporting away from Zendesk.

    15
  • Clik Rogan

    The BETA builder just isn't to par or even close to par in terms of its capability of reporting. It feels more of a variant than a full product itself. I use the BETA builder for customers who wish to present their dashboards on screens and TVs within their offices. However the classic builder I use to build reports for customers who intend on sharing these digitally or via email/print. 

    • What will happen to all the custom metrics & attributes customers are using now?
    • Will they be automatically available to use in the BETA builder?
    • Will we be able to customise the look & feel of the dashboard to meet customer needs?
    • Will it include bookmarks and the linking of filters across datasets so it's easy for end-users to preview data and interact with filters?
    14
  • mfg

    To date, this product does not meet our needs and development announcements have consistently declared that the new builder won't include business critical components of the existing builder. I do not feel comfortable assuming it will meet our needs and outlaying resources toward this product - we will likely need to transition to Power BI instead.

    Similar to other SaaS products when a new format is released, is there any need to deprecate classic? In other words, could this be considered for a 'containment' stage.

    Alternatively, is there any chance we could get more hands-on, one-on-one developer time to support the transition?

    13
  • Tobias Hermanns

    Converter available....??

    13
  • Amie

    I'd like to challenge the 61% figure mentioned in this post as I feel it's quite skewed. These 61% of users could be new users to utilising Zendesk Explore and don't know how to use the classic dashboard builder, so they opt for the beta version (which is totally fine for them and their needs) which is the simple option to use, yet lacking so many features. 

    I don't think it's fair for you to create a new version of a dashboard building and remove half the options which are currently present today and being utilised by a variety of people in order to build complex reporting and dashboards. 

    Explore takes a lot of time and effort to invest in building dashboards and reporting for more advanced users. This new dashboard experience should be a 1:1 comparative experience here. After assessing the comparison list here, a bunch of existing features from the classic dashboards are not being included in GA and post GA so It feels like we going to end up with a 1:-2 experience in the end. E.G Bookmarks, Images, legends, metric filters and export options to name a few. These are all valid features that businesses use to be able to report data back to stakeholders etc + not make their reports look boring.

    Zendesk users have gone from using Insights (100% customizable dashboards and reports) > to Zendesk Explore (which is about 80% customisable dashboards). The move to the new versions of the dashboard builder is pretty much dropping it down to 50% customizable now. 

    12
  • Ignacio de la Llave

    I agree with most requests here but specially one: Converting classic dashboards to the new builder automatically needs to be an option (both for Dashboards and, if the situation will be the same, for the report builder).

    4 years ago there was the migration from Insights to Explore, now this change. Recreating reports can have a very high cost and the return of investment that the new Dashboard will bring is, at least, questionable at the moment. Simplifying the migration should be a priority 

    11
  • Torsten Serfling

    So far we do not use the new builder, because there are still functional gaps relevant for us (e.g. scheduling and exporting reports).

    We have lots of dashboards, each for any product family we support. We want to show stakeholders only information relevant to them to keep the access easy and also for for data protection reasons. Rebuilding all these dashboards will create high efforts. Thus we have the same question as Terry.

    Any idea, when the new dashboard builder will move to GA? Q4/2023 or later?

     

    11
  • Vladimir Petrushenka

    This is just awful, and forgive me for being direct here. 

    We've spent months(!) putting together the existing dashboards, scheduling them to our partners, internally etc which now needs to be re-done completely. I'm talking about 200 dashboards. A fair question, that's been asked already, - who is going to pick the cost of that work for us? 

    But not only that, the key functionality that we currently use is no longer supported in BETA, so the product will be almost useless for us.

    Below is the list of what features aren't going to be available in the New builder (but please correct me if I'm wrong)

    • External sharing

    • Exporting

    • Scheduling

    • Multiple Tab Support (Color etc.)

    • Linking one filter to all reports in the DB and hiding it 

    • Image

    • Bookmark

    • Title options

    • Change metric

    • Change attribute

    10
  • Simon Boe Blouner
    Zendesk Luminary

    I completely agree with a lot of the concerns mentioned above!

    Especially:

    • Bookmark availability?
    • Converting classical dashboard to new?
    • Hidden filters?
    • And much more

    Please Zendesk, do not force your customers into settling with a "half-way-there" product upgrade/release once again - it ruins your credibility.

    8
  • AntonMi

    Second migration in 5 years without proper migration tool?

    8
  • Stephen

    Disappointing as we are still not seeing a decision on Bookmarks in the new builder. Without bookmarks, Explore Dashboards will be far more frustrating once the classic Dashboard is deprecated.

    8
  • Atanas Tomov

    I agree with all of the above comments. We manage several instances with a dozen of custom dashboards in each one, all build with the classic builder. The manual transition of each dashboard is going to require a lot of resources, time and planning.

    Unfortunately, we cannot even start early as some of the critical features are missing. One such feature which is rather simple is the lack of tabs.

    Please advise on proper dates as to when the aforementioned changes will take effect as we need to come up with a proper plan.

    7
  • Anastasia Kachanova

    Agree with other comments above. We are managing several zendesk instances, not one so in our case manual migration of all custom dashboards will be complicated.

    To be able to plan this migration on our side we need to see clear dates on GA launch, as we cannot start migration with half of critical features missing.

     

    7
  • Borja Cuadrado

    I think this change should no affect to all the current dashboards as many of us have invested several hours to create them. Maybe leaving the old ones, at least, should be an option or an automatic migration that shouldn't require us to spend even more time on this topic.

    On the other hand, what will eventually happen to functionalities such as bookmarks, delivery scheduling, hidden filters?
    The way you are considering it is not a migration as such, but a complete redesign, needing to rethink the solution taking into account the limitations of the new tool, leading to an unnecessary increase in dedication and for which many of our customers have already paid.

    Having to incur new costs makes it difficult to justify the use of Zendesk on a maintenance level, especially with future changes like this one

    7
  • Philipp Schumacher

    Hello ZenDesk Team,

    I feel very uncomfortable with this decision, you can't just discontinue our old reports. I put a lot of effort into these reports and now you tell me I need to recreate them? That is just very inefficient.

    A few months ago you announced out of the blue that certain placeholders can't be used anymore in automations. And now you pull this. My confidence in your services are shrinking as you actively reduce the benefits we have with your platform while rudimentary functions like ticket splitting, adding CCs via Makros or direct Team chats are still not available.

    In this case either a converter to the new builder is necessary or legacy support for the old dashboards. It is more and more difficult for me to justify the license costs to my management.

    7
  • Tom Erik Skjønsberg
    Zendesk Luminary

    Well then. Having seen the (lack of) feedback in the features post, I guess the only response we can give to this one is

    Thank you for letting us know that we need to start transition to a different reporting tool

    7
  • Stephen

    Hi,

    I have seen a number of people in this thread mention missing features in the new builder - here is a link to the features that will be included GA and beyond: Comparing features available in the dashboard builder 

    From my perspective, the biggest missing features that won't or aren't confirmed to be available are:

    I have not spent much time with the beta Builder, purely because of core missing features that I use frequently on Dashboards (bookmarks, hidden filters, scheduling, exporting, exclude filters).

    I would love to know how exporting / scheduling will look in the new builder as well. I haven't seen any information on these features and if they will be at least equivalent to the already existing functionality or if they are to be improved (which would be great).

    It's incredibly frustrating that there is no mention of tools to help move legacy Dashboards to the new builder, instead having to rebuild everything from scratch. In addition, there is going to be a usability loss for Support Managers in my business without bookmarks.

    6
  • Tobias Hermanns

    The impact is so high! We worked weeks on getting it ready!

    6
  • Paul Riscalla

    When does Phase 1 start? We would like to use the new dashboard builder, but we need to schedule dashboards. 

    6
  • John Tieu

    We have multiple client facing dashboards, is there a way to retain the link to the new dashboard for folks who have their dashboards bookmarked?

    6
  • Martin Cubitt

    Spot on Amie - Insights to Explore was bad enough, this is further and larger steps backwards and will surely push people to use other reporting tools and/or platforms for their support needs.

    5
  • Kaycee

    What!! We have done so much work to get our dashboards up to scratch and they are going to be useless! This shouldn't be allowed. Are we going to be reimbursed for the resource used to create the dashboards? Will there be a automatic migration? we have tried the beta dashboards and they are limited compared to the indepth we use. This isn't the first time this changes have happened which destroy work, when you changed the way drill-throughs were used then it destroyed alot of work and undid the basic drill-throughs.  

    5
  • Jon Thorne

    This just doesn't work at all for us, for many of the reasons outlined above. It's also a huge kick in the teeth for customers who spent months migrating from GoodData. Now we have to do it all over again, but with greatly reduced functionality that seems to be a massive retrograde step. I really hope this can be re-thought, as we invested fully into Explore and it's woven into so many of our business processes in its current form and functionality. We would seriously have to question whether Zendesk is right for us if this goes ahead.

    5
  • Darren Bell

    Just counted....we have a total of 55 dashboards, many of which have multiple tabs, in use by our end-users, agents, team-leaders and management.

    Generally it is myself who looks after these.... please confirm there is going to be an automated conversion process?

    5
  • Ryan Boyer

    Like many other comments, what are the steps to convert a current "classic" dashboard to the new dashboard? Is it a manual process or is there some kind of automation to the new experience?

    5
  • Reshma Patel

    I agree with the above comments and have many concerns about this change. We were forced to migrate from Zendesk reporting to Explore, and now you are asking us to move to these new dashboards. We don't have resources sitting around that can move all our dashboards over and scrap all the work they already put into building the current dashboards. Additionally, this is a redesign and will involve in-depth gap analysis as well as training for all our users. It should be a configurable option that admins that choose to enable if desired. If it's forced, you should have plans for automatic migration with minimal disruption to your customers and all existing features should be accounted for in the new design. 

    5

Article is closed for comments.

Powered by Zendesk