> 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/release-notes/inforiver-writeback-matrix/inforiver-writeback-matrix-march-2025-v4.2.md).

# Inforiver Writeback Matrix - March 2025 - v4.2

The bug fixes that are deployed as part of this release have been listed below:

### Column header alignment:

* The column headers were misaligned when the report had a single column dimension in the measure on rows layout. The alignment issue has been rectified.

### Infobridge:

* Cell-level formulas were not being captured in Infobridge in some cases like source refreshes. The issue where edited cells with applied formulas appeared as null in the query has been fixed.
* It was observed that rows inserted from Infobridge were sporadically failing to load in target reports. This has been rectified.

### Scenarios:

* Simulations run on formula measures that refer to forecast, data input, and native measures were not retained in scenarios. In the latest version,
   simulations on formula measures will be intact when switching between scenarios.
* The values in visual columns that were appearing as 0 in scenarios will now be captured accurately.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.inforiver.com/release-notes/inforiver-writeback-matrix/inforiver-writeback-matrix-march-2025-v4.2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.