diff --git a/.gitbook/assets/image (901).png b/.gitbook/assets/image (901).png
new file mode 100644
index 00000000..bd4da4b5
Binary files /dev/null and b/.gitbook/assets/image (901).png differ
diff --git a/.gitbook/assets/image (902).png b/.gitbook/assets/image (902).png
new file mode 100644
index 00000000..569e77f4
Binary files /dev/null and b/.gitbook/assets/image (902).png differ
diff --git a/.gitbook/assets/image (903).png b/.gitbook/assets/image (903).png
new file mode 100644
index 00000000..3ed7a084
Binary files /dev/null and b/.gitbook/assets/image (903).png differ
diff --git a/.gitbook/assets/image (904).png b/.gitbook/assets/image (904).png
new file mode 100644
index 00000000..7653b79d
Binary files /dev/null and b/.gitbook/assets/image (904).png differ
diff --git a/.gitbook/assets/image (905).png b/.gitbook/assets/image (905).png
new file mode 100644
index 00000000..252cc300
Binary files /dev/null and b/.gitbook/assets/image (905).png differ
diff --git a/.gitbook/assets/image (906).png b/.gitbook/assets/image (906).png
new file mode 100644
index 00000000..c695ad9f
Binary files /dev/null and b/.gitbook/assets/image (906).png differ
diff --git a/working-with-inforiver/12.-data-writeback/settings/advanced-settings.md b/working-with-inforiver/12.-data-writeback/settings/advanced-settings.md
index f8d13fab..a7df846e 100644
--- a/working-with-inforiver/12.-data-writeback/settings/advanced-settings.md
+++ b/working-with-inforiver/12.-data-writeback/settings/advanced-settings.md
@@ -1,12 +1,43 @@
# Advanced Settings
-In the advanced settings tab, you can enforce null checks on the data being written back. You can either exclude empty fields from writeback or prevent writeback altogether. In the Writeback settings _Advanced_ tab, the configurations listed below can be used to handle empty fields:
+### 1. Writeback column validation
-* Select the fields that require a null check to be performed before writing back.
-* Turn on the 'Prevent writeback when data is missing' toggle to stop writeback when empty fields are detected.
+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
-If null fields are detected during writeback, an exception notification is generated by Inforiver that gives details of empty measures/columns.
+Only the cells that are not null for the specified field will be written back to the destination.
+
+
+
+**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.
+
+In the sample report, for the Cumulative Revenue measure, notice how only the data cells with values greater than 500 million were written back.
+
+
+
+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.
+
+
+
+Whenever a writeback is triggered, Inforiver will display a preview of the excluded cells.
+
+
+
+**1.3. Prevent writeback when validation fails**
+
+Turn on the **Prevent writeback when validation fails** toggle to stop writeback when empty fields are detected.
+
+An exception notification is generated during writeback that gives details of empty measures/columns or rows that do not meet the validation condition.
+
+### 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 icon.
+
+In the example, we have renamed Segment to Category and Product to Brand. COGS has been expanded to Cost of goods sold.
+
+