13. Context awareness
Last updated
Was this helpful?
Reporting & Writeback Matrix Docs
Last updated
Was this helpful?
Inforiver provides built-in context awareness i.e., any comments, notes, data input, or even headers that you add will be updated dynamically based on external filter or slicer selection. You can even select writeback payload with Power BI filters.
When users enter comments or manually input data, the visual is unaware of the context, which can be set by a filter or a slicer in the report. In the example, notice how the comment entered for 'APAC' is still visible even after changing the filter to 'EMEA'.
With Inforiver, you can configure filter context, which ensures that Inforiver visuals are aware of context changes and responsive to changes in filters i.e. the comments, data input, writeback payload, etc are dynamically updated. Let's look at how to set up filter context.
Step 1: Click on the Filter Context button in the Insert ribbon.
Step 2: In the popup window, enter the table and field name for which context awareness is being set up. You can enter multiple tables and categories using the Add new link. In this case, we are setting up filter context for Subregions.
Step 3: Inforiver automatically generates the DAX code based on the tables and categories entered. Click on the Generate Dax button and copy the DAX.
Step 4: Create a new measure in your data model using the DAX generated in Step 3.
Step 5: Add the new measure to the Others (OM) visual parameter. It gets displayed in the report as well.
Step 6: Open the filter context configuration from the insert ribbon. You will now be able to select the new FILTERCONTEXT measure from the dropdown. You can enable/disable context awareness for notes and comments using the toggle switches. Click on save.
Let's see the context awareness feature in action by adding a notes column and setting a filter on APAC subregions.
Notice how the note is removed when we change the filter from APAC to EMEA.
Slicer selections will be reflected in header presets as well, if your report has been configured for filter context.
The filter selections are captured in the writeback table as separate columns. In the example below, the Segment and Region selections are captured as part of the writeback.
When the Segment and Region selection is changed to Corporate + Central, the notes and comments are inserted as separate rows in the snowflake destination and tagged against the changed categories.
With Inforiver, manual data entry fields like textboxes, dropdowns, or numeric input will also be responsive to slicer selections. Notice how the data inputs change according to the filter selections in the gif below.
The data input cells that are written back will also be determined based on filter selections. In the screenshot below, the report has 3 data input columns: Benchmark, Progress, and Status. Notice how the data input fields were written back to the snowflake destination for the Consumer + January + First Class selection.
When the selection is changed to Home Office + October + Standard Class, the data inputs corresponding to the selection are written back as shown below. The data input fields for each filter selection are captured as separate rows in the destination.
Individual measure headers can also be configured to reflect slicer selections. Double-click the measure header and click Ctrl + Space to open the suggestions panel. The list of slicers/filters will be displayed in the suggestions list. Select the filter name to append it to the measure header.
Notice how the slicer selection is reflected in the measure header.
After entering a data input value, users can choose to lock the cell to prevent other report users from overwriting the value. When you change slicer selections, locked cells will be retained. In the gif, notice how the Tax measure that is locked for Furniture is persisted even after changing slicer selections.
Connected planning reports often have varying granularities. For example, you may have a regional budget that is cascaded into a global budget target report. The target report is likely to have slicers on dimensions like quarters, product lines, tax segments, etc.
Inforiver’s built-in context awareness has been extended to Infobridge sources - enabling context-aware connected planning. Let’s look at a quick demonstration. Our bridge contains quarterly Discounts that we need to integrate into our yearly profitability report.
The target Yearly Profitability report contains data at year level. Before integrating the discounts from Infobridge, let’s use Inforiver’s Super Filter visual to set up context awareness in the target.
The target visual has data at a higher granularity, i.e. year-level and the source bridge has quarterly data. When we create an integration to the discount bridge, we need to map the Quarter dimension to the filter context measure in the target profitability visual.
Notice how the Infobridge measure, Discount, also changes in response to slicer selections.
