> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/5.-conditional-formatting/create-rule-reporting-matrix/field-value.md). # Field value You can assign fields from your dataset and apply conditional formatting based on the specified color. Let's consider a Benchmark dataset - each benchmark is represented by a designated color which is part of the source data.

Let's look at how to setup conditional formatting based on a field from your data source. Assign the text column containing the color scheme to the Writeback Matrix visual. You'll see a **Field value** option in the **Format by** dropdown. Select the text field that will be used to assign colors from the **Based on** dropdown.

Select the field that will be used to drive the color scheme

**Format font color** The font color for the Actuals measure is changed based on the Benchmark indentifier text field. To apply conditioinal formatting on the font color, select the **Font** option from the **Color for** dropdown.

**Format background color** To change the cell background color select **Background** from the **Color for** dropdown.

Apply cell background color from a source field

**Using Auto font color** When the **Auto font color** option is checked, Inforiver assigns a font color which will have maximum visibility against the backgroun color. Uncheck this option to assign a custom font color from the **Format** menu.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.inforiver.com/working-with-inforiver/5.-conditional-formatting/create-rule-reporting-matrix/field-value.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.