>

View settings needed to allow use in a Views Gadget?

Answered

Comments

7 comments

Date Votes
  • Seth Halvaksz

    Tagging Richard Marmura Martin Stephens on this question

  • Martin Stephens

    You can only add a view to a dashboard if it is available for the Main Subject Page.

    These options confuse most clients.  I have tried to clarify them below:

    The Main Subject Page shows all records for a subject.  Other pages may show a filtered view of that subject, based on a single related record.

    Example:

    • The Events section shows all events — this is the Main Subject Page for Events.
    • If you open a CRM Account, you might see an Events tab. That tab shows only the events linked to that account — a filtered view of the Event records.  This is one of the Subject Pages for Events.

    Currently, Dashboards are global only — they can’t display record-specific, contextual views. They’re limited to high-level reporting on Main Subject Pages.

    Seth Halvaksz

    But if Dashboards were enabled within individual records, it would unlock a whole new level of reporting power — giving users the ability to surface real-time, contextual insights right where the work happens.  They could replace many of our Crystal Reports.

    If any of this sounds familiar, it is because it is core to the idea I proposed to you and Rich!  :)

  • Seth Halvaksz

    Moved this post to the “Reporting: Best Practces” forum.

    Thanks Martin Stephens.  I remember you said that dashboards will not work for “record-specific, contextual views”.

    I know this is something Richard Marmura has on his list of enhancements for the future, but not yet on the roadmap, based on your suggestion.

  • Anthony Costantino

    Martin Stephens BUT, we can setup an Events view saved for main subject AND with filter on a specific Account. YOu need a view per account but it can be done for purposes of dashboards, right?

  • Martin Stephens

    Anthony Costantino that is correct.  Each widget on the dashboard can be filtered by a specific subject (e.g., Account, Event) using either View filters or Report filters, depending on the type of widget.

    This approach works well when you only need to focus on a small number of records—you can ‘hardcode’ the filters into the dashboard, creating a dedicated version for each record. 

    However, it becomes logistically unfeasible when trying to dynamically switch between many records.  Lets say you have 1,000's of accounts and you want to filter for a specific account.  In that case, you would need to manually update the filter on every individual dashboard widget each time you want to focus on a different record.  

    The above example is very relevant - with dynamic filters you could create the Dashboard “Account Profile” - enabling a holistic, data-driven view of account performance and growth opportunities.

  • Anthony Costantino

    yes, when i see this come up, it's usually in registrations or exhibitions, where a user (usually a sales leader or event manager) wants to track various metrics of a specific event or specific account within a dashboard. 

    Having a ‘dashboard’ within a subject would be very exciting for sales leaders and sales managers to see the performance of a single account; or on a single event they're trying to upsell to hit a target goal.

  • Linda Moyer

    Finally circling back, thank you Martin Stephens and everyone for your input! I've got the View Gadgets article updated.

Please sign in to leave a comment.