> Documentation index: https://www.gooddata.ai/docs/gooddata-ui/llms.txt lists every page of these docs as Markdown.

# IAttributeBody

- Package: [@gooddata/sdk-model](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-model/index.md)
- Kind: interface
- Source: https://github.com/gooddata/gooddata-ui-sdk/blob/rel/11.64/libs/sdk-model/src/execution/attribute/index.ts

Attribute is our nomenclature for 'dimension' as typically used in multi-dimensional BI modeling.

**Signature:**

```typescript
export interface IAttributeBody 
```

## Remarks

The attribute specifies on what dimension to slice/dice the measures.

In GoodData, each attribute can have multiple different display forms. Display forms essentially provide different representations for elements in the dimension.

## Properties

| Property | Modifiers | Type | Description |
| --- | --- | --- | --- |
| [alias?](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-model/sdk-model.iattributebody/index.md#iattributebodyalias) |  | string | _(Optional)_ This is user-assigned alias of the attribute; it is opaque for the backend. When backend returns metadata about execution results, it WILL include this user-assigned alias in the metadata. |
| [displayForm](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-model/sdk-model.iattributebody/index.md#iattributebodydisplayform) |  | [ObjRef](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-model/sdk-model.objref/index.md) | Reference to display form to use for element representations. The display form can be referenced by either URL of the display form resource on backend OR by unique, backend-recognized, identifier of the display form. Note: specifying display forms by URI is discouraged and WILL be deprecated in the future. The specification of URL has several drawbacks: - Display form URLs are tied to particular analytical workspace; this makes any application that uses URL-specified display forms workspace-specific. - Display form URLs are not supported by all GoodData backends == this makes any application that uses URL-specified display form backend-specific |
| [localIdentifier](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-model/sdk-model.iattributebody/index.md#iattributebodylocalidentifier) |  | [Identifier](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-model/sdk-model.identifier/index.md) | User-assigned id of the attribute. The value is used to cross-reference model elements that are part of an execution. The constraint is that the local identifiers of all measures and attributes in an execution definition MUST be unique. |
| [showAllValues?](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-model/sdk-model.iattributebody/index.md#iattributebodyshowallvalues) |  | boolean | _(Optional)_ Indicates whether to show all values of given attribute even if the data bound to those values are not available |

## Property details

### IAttributeBody.alias

This is user-assigned alias of the attribute; it is opaque for the backend. When backend returns metadata about execution results, it WILL include this user-assigned alias in the metadata.

**Signature:**

```typescript
alias?: string;
```

### IAttributeBody.displayForm

Reference to display form to use for element representations.

The display form can be referenced by either URL of the display form resource on backend OR by unique, backend-recognized, identifier of the display form.

Note: specifying display forms by URI is discouraged and WILL be deprecated in the future. The specification of URL has several drawbacks:

- Display form URLs are tied to particular analytical workspace; this makes any application that uses  URL-specified display forms workspace-specific. - Display form URLs are not supported by all GoodData backends == this makes any application that uses  URL-specified display form backend-specific

**Signature:**

```typescript
displayForm: ObjRef;
```

### IAttributeBody.localIdentifier

User-assigned id of the attribute. The value is used to cross-reference model elements that are part of an execution.

The constraint is that the local identifiers of all measures and attributes in an execution definition MUST be unique.

**Signature:**

```typescript
localIdentifier: Identifier;
```

### IAttributeBody.showAllValues

Indicates whether to show all values of given attribute even if the data bound to those values are not available

**Signature:**

```typescript
showAllValues?: boolean;
```