Adding Data for MyInsights Pages

Users can add data for MyInsights pages from the edit page. To navigate from the home page to the edit page, select the content name or select Edit from the Actions menu.

This displays the Data Palette tab, where users can add and preview data. The following data elements are available:

The following Salesforce field types are supported:

Salesforce Field Type MyInsights Studio Field Type
Auto Number String
Formula Field type of the result of the formula
Lookup String
Master-Detail String
External Lookup String
Checkbox Boolean
Date Date
Email String
Number

Float

Percent Float
Phone String
Picklist String
Picklist (Multi-Select) String
Text String
Text Area String
Text Area (Long) String
URL String
Currency (supported for query data elements)

Number

Currency symbols do not display in data previews.

Using the Context Query Data Element

Users can query a field value from the org based on the current user using the Context Query data element. The objects available depend on the selected content type.

Content Type

Objects

  • Account_Reports_vod
  • Account_Profile_Override_vod
  • KOL_Profile_vod
  • Account
  • User
Account_Plan_vod
  • Account
  • Account_Plan_vod
  • User
Inventory_Monitoring_vod
  • Account
  • Inventory_Monitoring_vod
  • User
Orders_vod
  • Account
  • Order_vod
  • User
Remote_Meeting_vod User
  • Territory_Insights_vod
  • Territory_Insights_Default_vod
User

Users can populate the following information when creating a query:

  • Object – A CRM object available for the selected content type for which the user has at least Read access
  • Field – A field on the object to display. Only fields for which the user has at least FLS read permission are available.

A context query returns a single record with a single field as output.

Using the CRM Query Data Element

Users can query data records from the org using the CRM Query data element. Users can populate the following information when creating a query:

  • Object – Any CRM object for which the user has at least Read access
  • Fields – Fields on the object to display. Only fields for which the user has at least FLS read permission are available. Multiple fields can be selected.
  • Limit (optional) – Number of records to display. The Preview displays a maximum of 200 records regardless of the limit.
  • Sort (optional) – Display order of the records based on field values
  • Where Clause (optional) – List of individual or grouped WHERE clauses joined by AND or OR. See Defining Where Clauses for more information.

A CRM query can return a single record or a list of records as output, depending on the limit defined by the user. Each record can contain one or more fields.

Using the Nitro Query Data Element

Users can query data from Nitro based on the current user using the Nitro Query data element. See Nitro Help for more information about Nitro.

To configure users for Nitro access, navigate to Setup > Custom Settings > VDS Settings and enter the appropriate profile in the VDS Profile setting.

Users must populate the following information when creating a query:

  • Table – Any Nitro table for which the user has at least Read access
  • Fields – Fields on the object to display. Multiple fields can be selected.
  • Limit (optional) – Number of records to display. The Preview displays a maximum of 200 records regardless of the limit.
  • Sort (optional) – Display order of the records based on field values
  • Where Clause (optional) – List of individual or grouped WHERE clauses joined by AND or OR. See Defining Where Clauses for more information.

A Nitro query can return a single record or a list of records as output, depending on the limit defined by the user. Each record can contain one or more fields.

Using the One for One Data Element

Users can add custom calculated fields for records in existing data elements using the One for One data element. Users must populate the following fields when defining the calculated fields:

  • Data Source – An existing data element. Only data elements with a list of records as output are available.
  • Fields – List of fields to display, including fields from the data source and additional calculated fields. After selecting the data source, all of the output fields for the data source display, but can be removed. Select Add to define a calculation for a new field. For each calculated field, users must define the field name and specify the type of calculation using expressions and a list of records from any existing data element.

A one for one calculation returns a list of records. Each record can contain one or more fields.

Using the Summarize Data Element

Users can calculate one or more custom field values using data from existing data elements using the Summarize data element.

For each calculated field, users must define the field name and specify the type of calculation using expressions and a list of records from an existing data element. Select Add to add a field.

A summarize calculation returns a single record with one or more fields as output.

Using the Today Data Element

Users can get the current date as a single record with a single value using the Today element. Users do not need to populate any additional information to retrieve this value.

Using the Object Translation Data Element

Users can get the singular and plural translations of an object name using the Object Translation element. These values can be used as labels and values in data and display elements. When the MyInsights page is deployed to users in a multi-country org, the labels are automatically translated in the correct language for each user. Users can select any CRM object for which they have at least Read access.

Using the Field Translation Data Element

Users can get the singular and plural translations of object field names using the Field Translation element. These values can be used as labels and values in data and display elements. When the MyInsights page is deployed to users in a multi-country org, the labels are automatically translated in the correct language for each user. Users must populate the following information:

  • Object – Any CRM object for which the user has at least Read access
  • Fields – Any fields for which the user has at least FLS read permission. Multiple fields can be selected.

Using the Veeva Messages Data Element

Users can query Veeva Messages from Veeva CRM using the Veeva Messages element. This element queries existing Veeva Messages, so users must create any custom Veeva Messages in their orgs before they can be used in MyInsights Studio. Users can use custom Veeva Messages as translations for custom text, for example, using a field calculated by a One for One element as a label. When the MyInsights page is deployed to users in a multi-country org, the Veeva Message in the correct language displays for each user.

Users can select Add to query multiple Veeva Messages at once. Users must populate the following information for each Veeva Message:

  • Category – Category of the Veeva Message
  • Name – Name of the Veeva Message

Using the Sort List Data Element

Users can sort a list of records from an existing data element by a calculated field using the Sort List element. A calculated field refers to any field created as a result of a data element, for example, the One for One element. Users must populate the following information:

  • Data Source – An existing data element. Only data elements with a list of records as output are available.
  • Sort By – A calculated field selected from the Data Source or a data calculation entered directly. Users can select Add to add fields, which are used to sort records in case of ties. Users can select the sort order for each field.

Using the Filter List Data Element

Users can filter a list of records from an existing data element using the Filter List element. Users must populate the following information:

  • Data Source – An existing data element. Only data elements with a list of records as output are available.
  • Filter by – A boolean expression. The results only contain records for which this boolean expression is true.

Using the Sublist Data Element

Users can get a subset of a list of records from an existing data element using the Sublist element. Users must populate the following information:

  • Data Source – An existing data element. Only data elements with a list of records as output are available. The order of the output records is maintained.
  • Skip this many – Number of records to skip, starting from the first record in the list.
  • Keep this many – Number of records to keep, starting from the record immediately following the last skipped record.

Defining Where Clauses for Query Data Elements

When defining Where clauses for a query data element to filter the data results, users must include a field on the queried object, an operator, and an expression. The expression can use data from other data elements. The operators available for selection in a Where clause depend on the data type of the selected field.

Field Data Type

Compatible Operators

Any (String, Number, Date, Bool)

  • Equals
  • Not equal to

Comparable (String, Number, Date)

  • Greater than
  • Greater or equal
  • Less than
  • Less or equal

String

In

Adding Data Elements

To add data elements from the Data Palette:

  1. Select Add Data Element.
  2. Populate the Name and Element Type fields.
  3. Select Next.
  4. Enter the appropriate information for the data element.
  5. Select OK.
  6. Select the refresh button in the Preview section to view the resulting data. Preview the data often to ensure the results are reasonable.

When all of the data elements are added, select Save. If there are no errors in the content, a deployable version of the content is created.

After adding and previewing the data, users can define the page layout. See Defining MyInsights Page Layouts for more information.