---
title: "Block settings for Transaction and Dimension Lists"
slug: "block-settings-transactions-dimension-lists"
description: "Explore block settings for Transactions and Dimension Lists, including configuration options, access rights, and data management in your application."
tags: ["applications", "Block Settings", "blocks", "boards", "Dimension List", "Modeling Formulas", "Reporting Data visualization", "Security Permissions", "Transaction List"]
updated: 2026-07-09T08:32:43Z
published: 2026-07-09T08:32:43Z
canonical: "kb.pigment.com/block-settings-transactions-dimension-lists"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pigment.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Block settings for Transaction and Dimension Lists

Block settings allow you to make structural changes and adjust different configuration options for each Block type. This article discusses the different options for Transaction and Dimension Lists.

To access Block settings, open your Application and in the left pane navigate to the Block, then select Settings, the cog wheel, in the top right. Alternatively, you can select the three-dot menu to the right of the Block’s name in Block explorer, and then select **Settings**.

## General

These are the different sections that can be found under the **General** tab in Block settings.

### Details

The **Details** section allows you to make adjustments to the List’s **Name**, **Folder** and **Description**.

### Display name

You have the option to set a **Display name** for the Block. This is a more user-friendly label that replaces the **Name** everywhere in the platform, except where uniqueness is essential (in Test & Deploy contexts and in formulas). You can hover over a name to show both the Name and the Display name.

You can specify a Display name in English and/or French. The version that appears for Members depends on their [language selection](/v1/docs/change-display-language).

### Data input

The **Automatically saves inputs** toggle allows you to turn off and on the [Autosave functionality](/v1/docs/deactivate-autosave). This setting defines whether Members’ edits and newly created Items are put into a draft mode until **Save** is selected or whether they are instantly saved.

### Default selector type

This setting controls the default [Page selector option](/v1/docs/use-selectors-context-views-boards) when the List is set to Pages. Single select allows users to select one Item in the List. Multiple select allows for multiple selections. This setting only impacts Views created after it is set. This means you can change it without impacting any existing Views.

### Item management

For more information on Test & Deploy, see [About Deploying Changes in Test & Deploy](/v1/docs/deploy-changes-test-environment#references-to-disconnected-items).

### List type

Available for both types of List, this setting allows you to change the List from Dimension to Transaction and vice versa.

> ℹ️ **Note**
> 
> If a Dimension List is used in the structure of a Metric, it must be removed from the structure before it can be converted to a Transaction List. If it is just referenced in Formulas, it can be updated.

### Duplicate

This section allows you to duplicate or create a copy of a List. When duplicating a Dimension or Transactions List, all Views are automatically copied.

### Application

Move List to another Application. Transaction and Dimension Lists are able to be moved from one Application to another. You can read more about moving lists in [this article](/v1/docs/move-a-list-to-another-application).

> [!WARNING]
> **⚠️** **Important**
> 
> When you move a List to another Application, the Access Rights of the new Application are applied to the List. Make sure you adjust the Access Rights configuration in the new Application.

## Special Properties

This section allows you to define the Default display name and default property.

### Default display name

The Default display name is used to select the Property that appears when a Dimension List is used in other Blocks. When selecting a Property to be used as the Display name, it needs to have the Text data type.

You can also translate your Dimension List Items into other languages and store them in a dedicated Property. For French, use [Translation rules](/v1/docs/block-settings-transactions-dimension-lists#translation-rules) (see below) to have them display only to your French-speaking Members.

### Default Property

This option is only in Dimension Lists and not used in a Transactions List.

The default Property, which must be unique, is used to determine which Property is used in situations where no other Property is specified.

Here is an example of a Formula referencing a Country List:

`Source_Metric[FILTER: Country."United States" OR Country.Region=Region."EMEA"]`

The Country List has a Region Property. In the first part of this formula, `Country."United States"`, there is no Property being specified and therefore the default Property is referenced.

In the second condition `Country.Region=Region."EMEA"` there is an explicit call out to the Region Property of the Country List.

#### List Item History Properties

These Special Properties store data about the time that Dimensions and Transaction List Items were created or edited and the user involved. For more information, see [List Item History Properties](https://portal.document360.io/e47cfe35-dc28-40c7-a083-6cf003073d8e/document/v1/view/1291b531-d21d-4a83-8a4e-1e8efe475d04).

#### Translation rules

You can choose to display French-language versions of your Dimension List Items to Members based on their language settings. For this:

1. Create a Property in this Dimension List to hold the translation of each Dimension List Item.
2. Select this Property from the dropdown found in the **Translation rules** section of **Special Properties**, under **French-speaking Members**.
3. If no selection is made, the Display name applies by default.

Once configured, the translations are displayed wherever the Items appear on Boards, Views, or Page selectors.

> [!NOTE]
> ℹ️ Note
> 
> English- and French-language versions are supported.

## Variables

For more information, see [How to use Item Variables](/v1/docs/use-item-variables).

## Subsets

For more information, see [How to Use List Subsets](/v1/docs/use-list-subsets)**.**

## Dependent Dropdowns

For more information, see [Dependent Dropdowns](/v1/docs/dependent-dropdowns)**.**

## Library

The Library section lets you toggle on the ability to share a List across multiple Applications. It also displays all the Blocks that reference or use the List.

### Share this Block with other Applications

The **Share this Block with other Applications** toggle enables this Block to be shared or referenced in other Applications. After this toggle is activated, it must also be activated in the Library of the Applications you wish to reference it in.

After a Block is shared, a formula can reference it using the following naming convention:

`'APPLICATION_NAME'::'BLOCK_NAME'`

## Block usage

**Block usage** shows you all the instances where the Block’s data is used or referenced in Blocks and Boards.

The Block type can be identified by its color, Blue for Dimension lists, Green for Transactions list, Red for Tables, and Purple for Metrics.

If a List Property references a List or uses the List in a Dimension-formatted data type, you see that List name. If it is used across multiple different Properties or formulas in a List, you see the List multiple times.

If a Dimension List is used in a Variable, the name of the Variable is listed with an X next to it.

## Security

Use the Security section to manage access rights configurations and data visibility for the List.

### List Item management

By default, List Item creation and deletion require the **Add List Items** and **Remove List Items** permissions, configured for the user's Role in [Blocks Permissions](/v1/docs/roles-permissions-access-rights#permissions).

For greater granularity and control, Pigment offers an option to **Enforce access rights check on Item deletion**. When this is enabled, Pigment introduces an additional verification step: it checks whether the user attempting the deletion has [**Write**](/v1/docs/introduction-access-rights#define-where-access-rules-apply) access for all Properties allowing manual input (i.e. excluding Properties computed by formulas).

> [!NOTE]
> ℹ️ Notes
> 
> - A Member without **Write** access cannot edit, input or delete. However, if you toggle the **Enforce access rights check on Item deletion** setting to **Off**, Members may now delete.
> - This setting applies whether Items are deleted through:
>   - manual Item deletion (for more information, see [Manage Items](/v1/docs/delete-items-dimension-transaction-list#use-manage-items-option))
>   - imports (for more information, see [Clear Items Prior to Import](/v1/docs/clear-items-prior))

### Access Rights

#### Property

This drop-down is used to define what Access rights configuration can be shown. This is because there is the ability to have different Access rights configurations on different Properties. Whatever Property is selected here determines the Access per Member, Configuration, and Inheriting access rights from sections.

> [!WARNING]
> **⚠️** **Important**
> 
> Members must have the **Define Application security** permission to access the **View detailed access per Member.**

#### Access per Member

The Access per Member section shows access by Member down to the individual Item. In the top left, you can switch between **Read** and **Write** Access to view the different types of access. You can learn more about **View detailed access per Member** in this article on [Access rights Inheritance](/v1/docs/understand-access-rights-inheritance/#access-per-member).

#### Block configuration

There are two settings in this section: **Data visibility management**, and **Access rights rules**. **Data visibility management** only applies to Read access rules. Lists can be **Based on rules** or **Public**. The **Public** setting overrides all access rights rules related to Read access and allows every user in your Pigment Workspace to read the data. This setting impacts all Properties of this List.

The **Access rights rules** section lists any access rights rules that have been applied to that List. Clicking on the rule opens the Metric used to create that rule and settings (the cog wheel) can be used to open the **Roles, permissions, & access** page.

#### Inheriting access rights from

This section will shows all of the blocks that are being referenced via a formula that contains access rights settings.

If you are using the User roles rule, you will most likely see all referenced blocks in this section. This is because the default User roles contain an application-wide access right setting.

When a Block is mentioned in this section, it does not mean there is necessarily a difference in the access rights.

If one Metric is referenced from another Metric, even if they have the same access rights, you see that Metric listed.

## Import configurations

The Saved import configurations section shows any saved Imports into the List. The name and description can be seen here. This is also where the [Configurations ID](/v1/docs/generate-import-config-id) need for API calls is saved and can be copied.

## Delete

This section can be used to delete the List.