Configuring MyInsights for Admins and End Users

Initial configuration includes the setup of all default functionality for MyInsights. Advanced functionality requires additional configuration.

Configuring MyInsights for Administrators

To configure MyInsights for admins:

  1. Grant admins the following permissions:

    Object

    OLS

    Record Types

    Fields

    FLS

    HTML_Report_vod

    CRUD

    Each record type corresponds to an entry point. Grant access to the record types for the appropriate entry points. See Components of MyInsights for more information.

    • Account_Plan_vod*
    • Account_Profile_Override_vod*
    • Account_Reports_vod***

    • Full_Speaker_Profile_vod

    • Full_Speaker_Profile_Default_vod

    • Inventory_Monitoring_vod
    • KOL_Profile_vod**
    • Orders_vod*

    • Remote_Meeting_vod

    • Territory_Insights_Default_vod
    • Territory_Insights_vod
    • Name
    • Platform_vod
    • RecordType

    Edit

    * Users can view HTML_Report_vod records of this record type without record type access.
    ** iPad users can view HTML_Report_vod records of this record type without record type access.
    *** Windows users can view HTML_Report_vod records of this record type without record type access.

  2. Enable visibility to the HTML_Report_vod tab.
  3. Place the Name, Platform_vod, and RecordType fields on the appropriate HTML_Report_vod object page layout.
  4. Place the Notes and Attachments Related List on the appropriate HTML_Report_vod object page layout.
  5. Assign the page layout to all profiles for the appropriate record type.

Configuring MyInsights for End Users

To configure MyInsights for end users:

  1. Grant end users the following permissions:

    Object

    OLS

    Record Types

    Fields

    FLS

    HTML_Report_vod

    R

    Each record type corresponds to an entry point. Grant access to the record types for the appropriate entry points. See Components of MyInsights for more information.

    • Account_Plan_vod*
    • Account_Profile_Override_vod*
    • Account_Reports_vod***

    • Full_Speaker_Profile_vod

    • Full_Speaker_Profile_Default_vod

    • Inventory_Monitoring_vod
    • KOL_Profile_vod**
    • Orders_vod*
    • Remote_Meeting_vod
    • Territory_Feedback_vod
    • Territory_Insights_Default_vod
    • Territory_Insights_vod
    • Name
    • Platform_vod
    • RecordType

    Read

    * Users can view HTML_Report_vod records of this record type without record type access.
    ** iPad users can view HTML_Report_vod records of this record type without record type access.
    *** Windows users can view HTML_Report_vod records of this record type without record type access.

  2. Populate the Sync Configuration Mode Veeva Setting with a value of 1. This setting adds support for multiple VMOCs per object.
  3. Activate HTML_Report_vod and Attachment VMOCs with platform-specific WHERE clauses for mobile platforms. For example, the HTML_Report_vod VMOCs for the iPad and Windows Tablet platforms include the following criterion in the WHERE clause:
    • Platform_vod__c includes ('Mobile_Device_vod')
  4. Alternatively, create a Full Sync VMOC for the HTML_Report_vod object and a secondary Full Sync VMOC for the Attachment object with the following suggested WHERE clauses:
    • Suggested where clause for HTML_Report_vod VMOC: WHERE ((Profile_vod__c = NULL) OR (Profile_vod__c = @@VOD_SF_PROFILEID@@)) AND (Platform_vod__c includes ('Mobile_Device_vod'))
    • Suggested where clause for Attachment VMOC: WHERE ParentId IN (SELECT Id FROM HTML_Report_vod__c WHERE ((Profile_vod__c = NULL) OR (Profile_vod__c = @@VOD_SF_PROFILEID@@)) AND (Platform_vod__c includes ('Mobile_Device_vod')))
      • If you have an active org-wide Attachments iPad VMOC, you can clone that VMOC and create an active iPad profile-level VMOC for the Attachment_vod object for the end user profile.
      • Only enable this VMOC for profiles with read access to the HTML_Report_vod object and read FLS to the Profile_vod field. Otherwise, the sync fails.
      • If using a profile specific VMOC for the Attachment VMOC, then a profile specific VMOC must also be created for the original VMOC attachment. This ensures the existing VMOC is applied to all profiles as part of the multiple VMOC feature.

      • The HTML_Report_vod and Attachment VMOCs can be modified to include Salesforce Files. See Using Salesforce Files in Veeva CRM with Lightning for more information.