Inforiver Writeback Matrix April 2025 - v4.4.2

This release includes the following fixes:

1. Inserting rows and measures with filter context in connected planning

Inforiver and Infobridge, both support filter context, allowing for seamless connected planning even while using slicers in one or both of the connected visuals.

Previously, if the filter dimension was a row, you could insert only rows from the bridge source or vice versa. With this update, you can now insert both rows and measures from the bridge source to the connected visual, regardless of whether your filter context dimension is a row or a measure.

Let's consider the example below:

  • A source visual in a bridge has three row dimensions: Country, Category and SubCategory.

Source visual in the bridge
  • The connecting visual has only two row dimensions: Category and SubCategory with the Country dimension added as a slicer to filter data based on country.

Connecting visual

Let's enable filter context in the above visual using Inforiver Super Filter.

Setting up filter context using Super Filter visual

While integrating these visuals, Inforiver lets you map the additional row (or measure) from the source to the connecting visual's filter dimension.

Filter dimension mapped

Despite the filter dimension being a row, you can now insert both rows and measures from the source to the connected visual, as shown below:

Inserted rows and measures from the source via the bridge

2. Missing Infobridge Writeback data in Azure SQL destination - for reports with more than 75 records

In the AWS environment, when Inforiver reports containing more than 75 records were written back via Infobridge, the writeback data was not present in the Azure SQL destination—even though the writeback was reported as successful. This issue has now been resolved.

3. Unable to delete a cell value in text measure - resets to default value

When a cell value in a text measure was deleted, it reverted to its default value rather than showing an empty cell. This bug has been fixed.

Last updated

Was this helpful?