topic Re: Change default views on Sales Dashboard, when dispayed as deal cards in Dashboards & Reporting

Change default views on Sales Dashboard, when dispayed as deal cards

MikevanBerkel — Wed, 14 Jul 2021 11:55:04 GMT

Hi,

I was wondering if there is an option to change the default view of the Sales Dashboard when the dashboard is displayed as deal cards?

I'm aware that it is possible to select a default view of the Sales Dashboard when all deals are displayed in table style. But this doesn't work when the deals are dispayed as deal cards.

Thanks!

Kind regards,

Mike

Re: Change default views on Sales Dashboard, when dispayed as deal cards

karstenkoehler — Wed, 14 Jul 2021 12:50:56 GMT

Hi @MikevanBerkel,

Unfortunately this is not possible at this stage, see also this thread.

For a workaround, you could bookmark a certain view in your internet browser. Each view has a unique URL.

Best regards!

Re: Change default views on Sales Dashboard, when dispayed as deal cards

MikevanBerkel — Wed, 14 Jul 2021 12:53:57 GMT

Hi Karsten,

Thanks!

I would be great if such an option could be implemented in the future. That would be very helpful!

For now I will work with the workaround.

Kind regards,

Mike

Re: Change default views on Sales Dashboard, when dispayed as deal cards

bcannon — Thu, 18 Aug 2022 13:49:03 GMT

I couldn't find anywhere in the community or in the Hubspot documentation as to whether this has been addressed. But I did find a way to set a default in the card view of Deals.

When accessing Deals, go to the List view rather than the Board view. Add the view you want to your tabs and move it to the first position. That becomes your default view - similar to how it works in Contacts. But by doing that, it also becomes your default view when using the Board view going forward.

Not sure that was intended or a nice by-product, but it appears to be the way to handle it as of now.

Re: Change default views on Sales Dashboard, when dispayed as deal cards

kvlschaefer — Thu, 18 Aug 2022 19:35:53 GMT

Thanks for sharing this workaround, @bcannon!