# Advanced Settings

### 1. Writeback column validation

In the advanced settings tab, you can enforce constraints on the data being written back. You can either use a formula to evaluate the data or use a null check.

#### 1.1. Cannot be empty

Only the cells that are not null for the specified field will be written back to the destination.

<figure><img src="/files/nEaNusujlsYR1ZE0CZzu" alt=""><figcaption><p>Cannot be empty option</p></figcaption></figure>

**1.2. Enter formula**

You can specify a formula that should evaluate to true for the cells to be written back. The cells that do not satisfy the validation rule will be excluded during writeback.&#x20;

In the sample report, for the Cumulative Revenue measure, notice how only the data cells with values greater than 500 million were written back.&#x20;

<figure><img src="/files/FR53hCaY52qVorAbnmWA" alt=""><figcaption><p>Cumulative revenue &#x3C; 500m not written back</p></figcaption></figure>

With this option, you can also apply cross-filters. Let's use the same validation rule, but this time in the Sum of COGS measure. The COGS cells that don't meet the cumulative revenue condition will not be written back.

<figure><img src="/files/mQzjZzXH7rGadRodAduC" alt=""><figcaption><p>COGS cells are excluded from writeback when Cumulative Revenue &#x3C; 500m</p></figcaption></figure>

Whenever a writeback is triggered, Inforiver will display a preview of the excluded cells.

<figure><img src="/files/v3Y1XRedCUPdRkGmATUi" alt=""><figcaption><p>Preview of excluded data</p></figcaption></figure>

**1.3. Prevent writeback when validation fails**

Turn on the **Prevent writeback when validation fails** toggle to stop writeback when empty fields are detected.&#x20;

An exception notification is generated during writeback that gives details of empty measures/columns or rows that do not meet the validation condition.&#x20;

<figure><img src="/files/L2RWfSrSEyop6xkxEizZ" alt=""><figcaption><p>Empty fields error</p></figcaption></figure>

### 2. Writeback column rename

You need not use the column names from the dataset while writing back, you can specify a custom column name. For instance, if the column name in the data set is PY, you can rename it to PreviousYear for writeback. To rename columns, navigate to Writeback settings > Advanced tab > Writeback column rename and click the <img src="/files/V4RoE01WPQ5fdmLqoPIJ" alt="" data-size="line">icon.

In the example, we have renamed <mark style="color:green;">Segment</mark> to <mark style="color:orange;">Category</mark> and <mark style="color:green;">Product</mark> to <mark style="color:orange;">Brand</mark>. <mark style="color:green;">COGS</mark> has been expanded to <mark style="color:orange;">Cost of goods sold</mark>.

<figure><img src="/files/7T2bxIBIl0QdOVOGx2J8" alt=""><figcaption><p>Renaming WB fields</p></figcaption></figure>

### 3. Schedule writeback

Inforiver will trigger writeback at the specified time you select without any manual intervention. You can specify the email IDs to be notified if a scheduled writeback job fails.

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

You can monitor the schedule history and view logs from the admin console. Click on **View jobs** to see the logs.

<figure><img src="/files/gVUVrMuXS60R9bQodMmj" alt=""><figcaption><p>Scheduled writeback logs</p></figcaption></figure>


---

# 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.inforiver.com/working-with-inforiver/12.-data-writeback/settings/advanced-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.
