Skip to content

Text components

Dashboard Publisher offers three text components: Heading, Paragraph, and Comments.

Allows the placement of text headers, for describing a section or displaying quotes or pullout text.

  • Component Name — enter a label for the component (optional). The label will not be visible in the dashboard; it is useful for identifying components quickly while laying out your dashboard.
  • Size — this changes the height or width of the component depending on the parent Container’s layout setting.
  • Text Editor — click the Fullscreen icon for comprehensive formatting options, or the More icon for quick access to text formatting tools.

Used to add a body of text for details, descriptions, or captions.

  • Component Name — enter a label for the component (optional). The label will not be visible in the dashboard; it is useful for identifying components quickly while laying out your dashboard.
  • Size — this changes the height or width of the component depending on the parent Container’s layout setting.
  • Text Editor — click the Fullscreen icon for comprehensive formatting options, or the More icon for quick access to text formatting tools.

Used to display open-ended verbatim comments as well as the outputs of various text analytics functions. The Comments component must be connected to a data source.

  • Name — enter a label for the component (optional). The label will not be visible in the dashboard; it is useful for identifying components quickly while laying out your dashboard.
  • Heading — edit the heading that will be displayed in the Comments component (default “Comments”). Click the Fullscreen icon for comprehensive formatting options, or the More icon for quick access to text formatting tools.
  • Size — this changes the height or width of the component depending on the parent Container’s layout setting.
  • Text Analytics — use Chips to display tagged chips on comment tiles. Choose None, Noun Chunks, POS Words (Parts of Speech) or Danger Words. The source data must contain the output you choose.
  • Tile Comment:
    • Is Eve Conversation — turn this on if the comments come from an EVE conversation, so each comment is formatted as a conversation transcript.
    • Text — in edit mode, the comment appears as {comment}. Do not remove the curly brackets surrounding the comment, otherwise the published dashboard will show static text rather than live data from the connected data source.
  • Tile Details — enter the content for the Details tab on each comment tile. Details are built from the supporting variables you added to the data source: add each variable as a placeholder in curly brackets, the same way {comment} works in Tile Comment. Leave blank to remove the Details tab.

Do Heading and Paragraph components need a data source?

No. Heading and Paragraph are static text components — you type the content directly using the text editor. They don’t connect to data sources.

Does the Comments component need a data source?

Yes. The Comments component must be connected to a data store to display verbatim responses. It does not support connecting to data explorations.

What happens if I remove the curly brackets from the comment tile?

The \{comment\} placeholder is what tells the dashboard to pull in live data from the connected data source. If you remove the curly brackets, the published dashboard will display the literal text “comment” instead of the actual verbatim responses.

What text analytics outputs work with the Comments component?

In the Text Analytics group, set Chips to Noun Chunks, POS Words (Parts of Speech) or Danger Words to display tagged chips on each comment — provided the connected data source contains that output.

Can viewers sort, search, or download comments in the published dashboard?

Yes. The Comments component includes built-in sorting and a search function that viewers can use to find specific comments. Comments can also be downloaded as an Excel file.

Comments can only be sorted by the supporting variables added to the data source. By default, they are sorted in descending order on the first supporting variable.

Can I display EVE conversation transcripts in the Comments component?

Yes. If your data source is from an EVE survey, turn on Is Eve Conversation in the Tile Comment group. Each comment is then formatted as a conversation transcript rather than a single block of text.

How can I change the size of a Comments component?

By default, the Comments component displays a limited number of rows. To increase the visible area, add the following CSS to your Dashboard Settings or Page Settings:

virtual-scroller.db-comment-dialog-scroll.vertical.selfScroll.ng-star-inserted \{
height: 700px !important;
\}

Adjust the height value to suit your layout.

How can I add an image to a dashboard?

To add an image to a dashboard page, you will need an image URL for an image hosted online. Avoid using the Dashboard Settings logo uploader to get a URL: uploading an image there replaces your dashboard logo.

Once you have an image URL, add a text component to the page and insert the image using the rich text editor’s image tool.

Why isn’t a supporting variable showing in Comments details?

If you’ve added a supporting variable to the Details section of a Comments component but no data is appearing, the variable may be in a multi-response format.

  1. Check the data format — if the variable is a multi-response type, you need to add the child variable(s) rather than the parent multi-response variable.
  2. Remove and re-add — remove the parent variable from the Details configuration and add the individual child variables instead.
Why can’t I find a comment variable, or why does my Comments component show an error icon?

Fields that have been excluded from exports and AI (for example, fields containing personal information) are withheld from Dashboard Publisher. They don’t appear in the variable lists when you connect a data source, and a Comments component that already uses an excluded field shows an error icon instead of comments. Choose a different variable, or ask the owner of the data to review the field’s exclusion setting.