# General Settings

General settings configure writeback behavior for a report. These settings control how data is structured, filtered, and written to the destination.

### 1. Writeback type

Use **Writeback type** to define the table structure. There are four supported types.

<figure><img src="/files/iDkAUGP96R2wPJqalr6q" alt=""><figcaption></figcaption></figure>

#### 1.1 Long

**Long** is the default writeback type. Each row represents an observation, and each column represents a variable. Only **Long** supports writing back **comments** and **notes**.

<figure><img src="/files/paVWgKBZIoXAdmw2tuXw" alt=""><figcaption></figcaption></figure>

#### 1.2 Wide

**Wide** stores measures as columns. As you add more measures, the writeback table adds more columns to accommodate them. Totals and subtotals are not written back in **Wide** format.

<figure><img src="/files/HPeOlGLvlbM6oJf6F3VZ" alt=""><figcaption></figcaption></figure>

#### 1.3 Long with changes

**Long with changes** uses delta writeback. Only changed values are written in the report. Previous values are stored in **PreviousValue**, and new values are stored in **Value**. The system also sets **IsLatest = 1** to identify the latest row. Delta writeback works for both numeric and text data type adjustments.

<figure><img src="/files/uuWvTAaCxp7Wd7cBgFyI" alt=""><figcaption></figcaption></figure>

#### 1.4 Wide with changes

**Wide with changes** uses delta writeback, but each measure is stored in a separate column. It maintains change history and uses **IsLatest** to identify the active record.

<figure><img src="/files/3DHdmQPPMtEuPhxIptxk" alt=""><figcaption></figcaption></figure>

#### Writeback type considerations and best practices:

1. After the first writeback, changing the **Writeback type** displays a warning before existing tables are unselected in **Writeback > General Settings > Destinations**. You can reselect the table for writeback, but the system checks for conflicts between the existing table type and the current **Writeback type**. If a conflict exists, the system prompts you to drop and write back the table. When in doubt, create a new table and perform writeback instead of dropping an existing one.
2. Changing row or column dimensions displays a warning before it drops and writes back the table.

### 2. Filter

Use **Filter** to control which data gets written back to the destination. The filter list includes predefined options and custom filters

<figure><img src="/files/sKiFEfOT7FG8ddOrnSbT" alt=""><figcaption></figcaption></figure>

#### 2.1 None

**None** writes back the entire report or scenario without applying any filter.

#### 2.2 Data with Comments only

**Data with Comments only** writes back only the cells that contain comments. This option works only with the **Long** writeback type.

#### 2.3 Calculated rows only

**Calculated rows only** writes back only calculated rows, including any notes added to those rows.

### 3. Additional column configuration

Use **Additional column configuration** to add date keys to the writeback table during writeback. This requires consent to access all datasets in the workspace.

**Add Date Key** adds a **Date Key** column to the writeback table. For high-level planning scenarios such as revenue by year or month, the system appends the first day of the month or quarter to the date dimension. For example, if the report is set to Year-Month, the system writes **01-01-2025** for **Jan 2025**.

**Add Date Key** works only when a time intelligence date hierarchy is used in the **Columns** field.

<figure><img src="/files/aHjQ7mwSsSTd9d59ysfK" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/mrpDzojoTlRVWvtZ6VKn" alt=""><figcaption></figcaption></figure>

### 4. Decimal Precision

Use **Decimal Precision** to define the number of digits after the decimal point. This is a one-time setting that applies to all destinations configured for a report page. When you configure the first writeback destination, the system displays a dialog to set decimal precision.

<figure><img src="/files/beGX1zXif9MAZvbLOcui" alt=""><figcaption></figcaption></figure>

You can configure numeric data with up to 10 decimal digits. Any digits beyond 10 are rounded off.&#x20;

<figure><img src="/files/ASkMklC60IFimQ1uh3Gz" alt=""><figcaption></figcaption></figure>

The configured precision appears in the **Decimal Precision** section.

<figure><img src="/files/frTRnC0mXCL8PmyRNBtR" alt=""><figcaption></figcaption></figure>

### 5. Text field length

Use **Text field length** to control the number of characters written back for text fields. The default limit is **512 characters**. When you add the first destination, you can either keep the default limit or allow writeback up to the maximum supported by the backend. This is also a one-time setting for all database destinations on that report page.

<figure><img src="/files/jJi0b0bc9J8Njhz4tuuZ" alt=""><figcaption></figcaption></figure>

The **Text Length** section of the report shows the set text length as follows.

<figure><img src="/files/Cm9mT6Xaho9u3kzQwrNI" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If the **Text length** exceeds the configured limit, **writeback fails**.&#x20;
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fabricplan.com/planning-sheets/how-tos/persist-planning-data-using-writeback/general-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.