Share Via
Veeva MyInsights Dashboard Components: A Must-Know Guide for Developers
A strong MyInsights dashboard in Veeva CRM begins with the right initialization setup. This blog outlines the essential components every developer must understand—Entry Point, Content Zip File, and the HTML_Report_vod record—to ensure smooth deployment and real-time usability. Gain clarity on how these parts work together to power your dashboard experiences.
Developing impactful MyInsights dashboards in Veeva CRM starts with more than just front-end design. At the foundation lies a set of core initialization components that govern where the dashboard is accessed, how it’s delivered, and what content it renders. Understanding these elements—Entry Point, Content Zip File, and the HTML_Report_vod record—is critical for developers aiming to build scalable, responsive, and CRM-integrated dashboard experiences.
Let’s explore the three key initialisation components that every MyInsights dashboard relies on:
Entry Point
The Entry Point defines where in Veeva CRM a MyInsights dashboard will launch. It serves as the activation trigger for displaying the dashboard, tailored to specific CRM pages or business objects.
Why Entry Points Matter:
- Determine when and where a dashboard appears in the CRM workflow.
- Allow contextual dashboard access (e.g., on an account page).
- Support both standard and custom objects.
How Entry Points Work:
- Configured through MyInsights Studio for standard dashboards.
- Configured directly on the HTML_Report_vod record for custom dashboards.
- Each entry point maps to a specific record type within the
HTML_Report_vodobject. - Multiple dashboards can use the same entry point with conditional rendering logic.
Common Use Cases:
- Launching dashboards from Account, Call, or Order pages.
- Displaying tailored insights during Remote Meetings.
- Showing field-force KPIs at the Territory level.
Entry Point to Record Type Mapping:
To properly display a MyInsights dashboard at the right time and place in Veeva CRM, the system needs to know which record type the dashboard belongs to. This mapping ensures that when a user navigates to a page like an Account or Call Report, the correct dashboard is triggered based on the defined record type.
| Entry Point | Record Type |
|---|---|
| Account | Account_Reports_vod |
| Account Plan | Account_Plan_vod |
| Call | Call2_vod |
| Default Account Profile | Account_Profile_Override_vod |
| Default KOL Profile | KOL_Profile_vod |
| Inventory Monitoring | Inventory_Monitoring_vod |
| Orders | Orders_vod |
| Remote Meeting | Remote_Meeting_vod |
| Territory | Territory_Insights_vod |
| Default Landing Screen | Territory_Insights_Default_vod |
| Territory Feedback | Territory_Feedback_vod |
| Speaker | Full_Speaker_Profile_vod Full_Speaker_Profile_Default_vod |
These mappings ensure dashboards are rendered correctly based on the CRM context and associated record type. By configuring the entry point effectively, organisations ensure that field reps access dashboards at the most relevant moments during their CRM workflow.
Content Zip File
The Content Zip File contains all the static assets required to render a MyInsights dashboard:
- HTML
- CSS
- JavaScript
- Image
Key Features:
- Deployed using MyInsights Studio or via Vault integration.
- Supports both simple dashboards and complex data visualisations.
- Must be well-structured and optimised for loading performance.
Best Practices:
- Compress files efficiently before upload.
- Maintain consistent naming conventions.
- Ensure external dependencies (if any) are bundled or referenced correctly.
The content zip file is the engine that powers the user interface—its structure and integrity directly affect performance and reliability.
MyInsights Record (HTML_Report_vod)
The MyInsights Record, stored in the HTML_Report_vod_c object, acts as metadata that binds the dashboard’s technical files with its logical context in the CRM.
Key Attributes:
- Name: The unique dashboard identifier
- Entry Point: Links to a specific object or page
- HTML_Report_Type_vod_c: Determines if the dashboard is standard or embedded
- Status: Indicates the lifecycle stage of the dashboard (e.g., Draft, In Progress, or Published) and determines whether it is visible to end users.
This record is essential for registration and versioning of dashboards. It ensures proper mapping between the Entry Point and the correct Content Zip File.
Conclusion
Successfully deploying a MyInsights dashboard in Veeva CRM requires more than effective design—it demands a deep understanding of its initialisation architecture. The Entry Point, Content Zip File, and HTML_Report_vod record work together to define the dashboard’s behavior, accessibility, and data context. When properly configured, these components ensure a consistent and seamless user experience, enabling developers to deliver performance-optimised and business-aligned visualisations for the field force.
