---
title: "View Automation Settings"
canonical: "https://wiki.yellowfinbi.com/space/yfcurrent/2196805/View%20Automation%20Settings"
format: markdown
---
> Macro (anchor)
> Macro (toc)
## Overview
Automation settings can be configured for most Views. These settings control various automated assistance features - both AI-enabled and pre-AI features. These features can be turned on or off at View level. Careful consideration should be given to which AI features are enabled, as usage of these features will incur token usage on your AI account.
Individual fields can also be enabled and disabled for use by AI features through the **Key Variables** tab. Certain AI features require actual data to be sent through to the external AI model. Fields containing sensitive, private or confidential information should only be enabled in accordance with your organisation's policies.
## Accessing the Automation Settings dialog box
To access the **Automation Settings** popup, follow the steps below.
1. Navigate to the Browse Page and Filter to show just Views.
2. Right click on the View you want to configure - and Select Edit / Automation Settings,
3. The Automation Settings popup will be displayed.
> ℹ️ You can also access a view's **Automation Settings** dialog box while you're editing a view (whether you're modeling or preparing). Look for the **Automation Settings** tool, along the top toolbar and click on it for fast access.
> ℹ️
> ℹ️ 
---
## Understanding the General Settings tab
The **General Settings** tab of the **Automation Settings** dialog box displays options for configuring automation features including AI features, Guided NLQ and Assisted Insights.
The table below describes all the options that are available.
| Field Name | Field Description | Default |
| --- | --- | --- |
| Enable View for Assisted Insights | Toggle this on to enable Assisted Insights and Signals for this view. This is the only mandatory option on this page for enabling Assisted Insights. The optional settings will, however, further improve the Assisted Insights experience. | Off |
| Enable View for NLQ | Toggle this on to enable Guided or AI-enabled NLQ for this view. | Off |
| Enable AI Build Report | Toggle this on to enable the AI-enabled Build Report tool within Conversational Analytics. | Off |
| Enable AI Create Story | Toggle this on to enable the AI-enabled Create Story tool within Conversational Analytics. | Off |
| Enable AI Follow-up Question | Toggle this on to enable the AI-enabled Follow-up Question tool within Conversational Analytics. | Off |
| Enable View for Tell Me About My Data | Toggle this on to enable the Tell Me About My Data feature for this View. | Off |
| Row Unique Identifier | If you have a field in your view that acts as a unique identifier, select it from the list. This is used by Assisted Insights. | None |
| Primary Date Field | This drop-down is used for Signals and Guided NLQ. Select the default date field for either or both to use.
In Signals, this field is used to pre-populate the date field in **Step 3: Time & Schedule** when setting up a new signal.
When your Guided NLQ question or Assisted Insights data contains the date range, Yellowfin will retrieve your results based on the field you select as the primary date field. Bear in mind that choosing different date fields will likely change your results.
For example, setting your primary date field to an invoice date field will produce different results to a payment received date field. If you queried your invoice date field for invoices dated January 1 this year, the total invoiced amount on that day would differ to a subsequent query on January 1 this year for payments received.
When you select a field from this drop-down, an additional field called **Scope of Analysis - Date Period** will appear below it and is used solely for Assisted Insights. | None |
| Scope of Analysis - Date Period | This field is used only for Signals, and only appears after a **Primary Date Field** has been selected. It is used to set up [default granularity](https://wiki.yellowfinbi.com/space/yfcurrent/2204122). | None |
| Default Date Period - NLQ | Set a default period for Guided and AI NLQ. This will be added to the query if the user does not specify a date period. Note that Guided NLQ requires the Primary Date Field to be selected for this setting to work. | All Time |
| Custom Help Text - Guided NLQ | Add content to this text field if you wish to display any specific text for the current view. When using this view with Guided NLQ, this text will be displayed on the drop-down for switching views, alongside the view name and description. | None |
> ℹ️ The **Automation Settings** dialog box won’t save your settings until you’ve clicked the **Submit** button on the **Key Variables** tab. Any time you visit the **Automation Settings** dialog box, you must continue on to the **Key Variables** tab and click on **Submit**. This saves any changes to both tabs of the dialog box.
---
## Understanding the Key Variables tab
After enabling the required automated features (AI, Assisted Insights or Guided NLQ), you can configure field level settings on this tab. The Key Variables tab provides for field-by-field configuration for various field settings. Some of these settings apply throughout Yellowfin (ie. chart default colours) and some apply only to AI, Assisted Insights or Guided NLQ functions.
The **Key Variables** tab is divided into sections for metrics, dimensions, dates and filters (if any filters exist). Scroll down the dialog box to see the different sections.
| **Field name** | **Description** | Field type | **Usage** | **Default** |
| --- | --- | --- | --- | --- |
| – | A dropdown on the left displays any default aggregation applied to the field. This can be edited from the dropdown if required. | Metric | System-wide | Sum |
| – | The field name can be edited here, but note that it will be updated everywhere else it’s used (the view, reports etc.). | Metric, dimension, date | System-wide | Column name from the table the view field came from |
| Assisted Insights | Use this checkbox to include or exclude a field for Assisted Insights. If you don’t see a column for Assisted Insights, make sure you have enabled Assisted Insights at View level (see the [General Settings](https://yellowfin.atlassian.net/wiki/pages/resumedraft.action?draftId=250740901&draftShareId=a3e26283-497f-4a7d-8fee-ae340a1c2154) tab section), and that your role has the Configure Assisted Insights box checked.
If the checkbox is greyed out, check for these situations and correct, if necessary.
- You selected the field as the view’s Primary Date Field in the previous steps.
- The date field has been formatted using an unsupported formatter such as the datePart formatter (they should be formatted using the DateFormatter or Timestamp formatter for use with Assisted Insights). | Metric, dimension, date | Assisted Insights | Unchecked |
| Enable for NLQ | Use this checkbox to include or exclude a field for Guided NLQ and AI NLQ (Build Report). If you don’t see check boxes for this column, make sure you have enabled NLQ at View level (see the [General Settings](https://wiki.yellowfinbi.com/space/yfcurrent/2196805) tab section), and that your role has the Guided NLQ Manager box checked.
If the checkbox is greyed out, check for these situations and correct, if necessary.
- You selected the field as the view’s Primary Date Field in the previous steps.
- The date field has been formatted using an unsupported formatter such as the datePart formatter (they should be formatted using the DateFormatter or Timestamp formatter for use with Guided NLQ).
- The field is part of a date hierarchy. Date hierarchies work on [granularity](https://wiki.yellowfinbi.com/space/yfcurrent/2227273) (for example, year, month, week day), and each date field in a hierarchy is automatically checked and greyed out to prevent unchecking to ensure the hierarchy functions correctly within Guided NLQ. | Metric, dimension, date, filter | NLQ only | Unchecked |
| Share with AI | Checking this will share actual data with AI models when using AI Create Story or AI Follow-up Question modes. Care should be taken to ensure these selections comply with your organisation’s security policy. | Check box | AI Create Story
AI Follow-up Question | Off |
| Plural (dimensions only) | Only editable if a field has been enabled for either Assisted Insights or Guided NLQ.
In Guided NLQ, this will ensure that plurals are shown as needed when someone is asking a question, and when certain types of results are displayed.
In Assisted Insights, plurals are used in the narratives it creates. | Dimensions | Assisted Insights, Signals and Guided NLQ | — |
| Description | Updating the field description here will update it throughout Yellowfin. It can also be accessed and updated when editing a view in Prepare mode. The description is often displayed when hovering over a field name — in the view, in Report Builder and in Chart Builder | Metric, dimension, date, filter | System wide | — |
| Higher value is | This dropdown lets you choose if higher numeric field values are classed as ‘good’ or ‘bad’. For example, a higher profit margin value is typically good, but a high cost value is typically bad.
Results considered 'good' are displayed in blue and 'bad' in orange in charts and narrative for Assisted Insights and Signals, and in ‘Difference’ questions in Guided NLQIn Assisted Insights, it displays an arrow showing the sentiment of a KPI. | Metric | Assisted Insights, Signals and Guided NLQ | Good |
| Format | This dropdown lets you customize the format of metrics and dates. For example, you can use the typical date format options to display a yyyy-MM-dd date as MM d yyyy.
Options for metrics are different to options for dates. For dates, take a look at the options on the Custom button, which provides additional settings. | Metric, date | System wide | — |
| Granularity | This column is displayed only if the date field uses DateFormatter or TimestampFormatter. Use this field to see and set the date granularity with one click using this dropdown menu. [Learn more about granularity](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2227273). | Date | System wide | — |
| Non-Additive | This field is reserved for future use. | — | — | — |
| Custom Chart Color | Any custom chart colors set here will be used when Yellowfin creates charts. | Metric | System wide | — |
| Filter Value Case | Selecting Uppercase or Lowercase for this field activates a backend operation which converts the filter value into the selected case. Anything you set for a field here will be used when Yellowfin runs an SQL query with this field. It is never reflected in how field values are displayed in reports or other content produced by Yellowfin. | Dimension | System wide | — |
| Mandatory Filter | If a dimension or date field has this option set, it must be included with every Guided NLQ question.
In Guided NLQ, an orange dot will appear next to mandatory fields in the dropdowns.
In reports, mandatory filters must be included at the Report Builder stage, although when published, the filter can be left without any values selected. | Dimensions, date | System wide | — |
| Field Usage Restrictions | This red checkbox works differently to the blue tick-style checkboxes. If a red checkbox on the dropdown is checked, some restrictions have been applied. Click on the dropdown to see the full list.
The Load Filter Values is used only for Guided NLQ. For fields with many values, this option can be disabled (red cross on) to prevent Yellowfin from querying the database for possible values when Guided NLQ displays the field values as a list. This can improve performance of the system. The user can instead type a value. | Metric, dimension, date, filter | System wide (excluding Load Filter Values which is used for Guided NLQ only) | For metrics and dimensions, **Restrict by Access Filter** and **Filter text suggestions** are restricted (checked).
For non-date hierarchy dates, **Drill Anywhere** and **Restrict by Access Filter **are restricted (checked).
For dates that are part of a date hierarchy, **Restrict by Access Filter **is restricted (checked). |
All of the above fields can be enabled and/or configured for via the **Automation Settings** dialog box. As noted in the table, some of these settings may also affect other areas of Yellowfin. Make sure that you are aware of shared settings before you save any changes.
For more information on how to use these settings for specific functionality, such as [Guided NLQ](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2196305), please see the relevant section of the wiki.
---
## Setting field usage restrictions
Administrators can influence how data is made available and used at report level by customizing these settings. For example, you may wish to prevent a field from being displayed as a column in a report table if its main purpose is to facilitate an advanced function.
Note that most of these restrictions apply to content used from reports with the exception of Load Filter Values, which is used exclusively for Guided NLQ Refer to the table below for further details.
| Restriction | Description |
| --- | --- |
| Display Column | Checking this box hides the column from displaying in reports and charts. It is still visible in the Report Builder, in the list of columns above the table, although its contents are not displayed in the table. See [Field Settings](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2204259) for further details. |
| Grouping | Checking this box hides the **Group Data** option from the field's column dropdown in the Report Builder. See [Field Settings](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2204259) for further details. |
| Drill Anywhere | Checking this box prevents the Drill Anywhere option from being available in the Report Builder. See [Field Settings](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2204259) for further details. |
| Sort Column | Checking this box hides the **Sorting** option from the field's column dropdown in the Report Builder. It also hides the Sorting option in the column's formatting settings. See [Field Settings](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2204259) for further details. |
| Calculations | Checking this box disabled the field from being used as part of a calculated field. See [Calculated Fields](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2196681) for further details. |
| Restrict by Access Filter | Checking this box disables access filter restrictions on this field, so no restrictions apply. See [Restricting Data with Access Filters](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2196295) for further details. |
| Filter text suggestions | Checking this box disables the option to use text suggestions with user prompt filters. See [Filter Text Suggestions](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2204259/Field+Settings#fieldpermissions) for further details. |
| Load Filter Values | **Load Filter Values** is used only for Guided NLQ. For fields with many values, checking this box disables Yellowfin from querying the database for possible values when Guided NLQ displays the field values as a list. This can improve performance of the system. The user can instead type a value. See [Setting up Guided NLQ](https://yellowfin.atlassian.net/wiki/spaces/yfcurrent/pages/2196305) for further details. |