Reporting Matrix FAQ

Visit Microsoft Appsource to purchase licenses for Reporting Matrix. Subscription is available by tier and the fee varies based on the plans. To learn how to set up, pay for, and manage licenses for custom Power BI visuals purchased from AppSource, refer to this article.

For other Inforiver licensing related queries, visit the General FAQ page.

Yes. For bundling (OEM) Inforiver fully or partially with your own products or services to your customers or any third party, separate licensing plan is available. This would be based on the number of developers or customers. Contact us to learn more.

Yes. For embedding Inforiver fully or partially with your own products or services, separate licensing plan is available. This would be based on the number of developers. Contact us to learn more.

YES. You can input and create new budget/forecasts in seconds.

You can (a) Create forecasts based on past sales data, (b) Create forecasts using a blank template, (c) Allocate forecasts across countries or product categories proportional to past performance, (d) Perform dynamic what-if simulations to adjust forecasts using a slider interface (e) Comment and annotate on budgets, forecasts, plan, or variance data points, and (f) writeback forecast data along with notes & comments.

Refer to
1. Manual Input for Budgets - Data input, simulations, commenting and writeback
2. Advanced Forecasting & What If Simulations in Microsoft Power BI - 5 ways to run dynamic what-if simulations in Power BI
3. Entering Forecasts, Comments and Write Back - Forecasting Multiple Items with Seasonality in Power BI

You can use Inforiver data input templates to gather your budgets, forecasts, plans along with comments using row level security. For an advanced and connected xP&A / FP&A solution, we recommend ValQ. We are working on modernizing ValQ so that it can integrate with Inforiver's data & commentary input templates. ValQ is a separate offering requiring a separate subscription. Note that ValQ can be used for xP&A, FP&A and value driver planning.

Inforiver writeback allows users to post the data and comments from the visual to a supported destination. Writeback is supported only in Writeback Matrix and the following destinations are supported

• Database – Azure SQL, Dedicated SQL Pool, Azure Data Lake Storage, Databricks, Snowflake, Amazon Redshift, BigQuery, SingleStore, SQL Server, SAP HANA, Oracle, Fabric Lakehouse, Fabric Warehouse, Dataverse, PostgreSQL and MySQL
• OneDrive and SharePoint – Writeback file as a CSV to the selected folder
• URL – HTTPS post with the CSV as payload to a configured endpoint

Yes. Inforiver can be used in small form factors just like native Power BI table/matrix. Inforiver works with slicers and other native visuals and supports multiple cross-filtering.

Inforiver supports collaboration with other users through real-time commenting, email notifications, scheduled excel & pdf reports and commentary digests.

Users can post, reply, and mention users; email notifications are sent on reply and mentions. Authors can restrict access on who can post comments in the visual. Comment digests can be scheduled at custom intervals which summarizes all comments made between each run.

However, these options are available only with Writeback Matrix.

Yes, users can be notified using commenting. @ can be used to lookup the list of users from one’s organization. This feature is available only in Writeback Matrix.

With our Writeback Matrix edition – you can save your theme, settings etc., and it would automatically download them based on your user profile as corporate theme and default settings. 

Because we are limited to the 3 MB custom visual size - we are not able to support all the fonts with the Export to PDF feature (each font family is 1MB in size).

Writeback Matrix Edition customers however can use any custom font in the subscription scheduler for the export to PDF feature as this edition comes with database storage where additional font styles including custom corporate fonts can be stored.

Inforiver's default font is Antikor Mono which is similar to Segoe but is monospaced for numerals. Learn why we feel this font offers the best value for tabular reporting.

All editions support formatted paginated export to excel in WYSIWYG with structure, format, and notes as is. The Reporting Matrix edition provides additional customization options for Export to Excel, and they support Export to PDF too. Note: Export to PDF and Excel is possible only in Power BI Service (and not the Desktop). Once you publish your reports, the options should get enabled.

We offer a formatted and paginated export solution. So, there is a limit of 30k rows for Excel and 1000 pages for PDF for performance and fidelity reasons on the quality of export.

Yes. Inforiver scheduler supports custom scheduling of reports to email and other external destinations like OneDrive, SharePoint and Teams. Burst and broadcast of paginated reports honoring row-level security (RLS) is also possible. This is supported only in Writeback Matrix.

Inforiver works best with summarized and aggregated data. Your data model could contain billions of rows, but we recommend that using Power BI slicers you restrict the data assigned to Inforiver to be in summarized in nature.

Inforiver works in two different configurations: default and performance mode.

In the default mode, Inforiver retrieves all hierarchy levels from the semantic layer. This is done in order to provide advanced features at the visual level (like custom aggregations). However, Power BI brings only one hierarchy level of data at a time using a windowing technique. In a sense, it only fetches what you can see at a time. As Inforiver is architecturally different from Power BI, we recommend that you do NOT compare the performance of Reporting matrix vs Power BI Matrix.

Effective release 2.7,  Reporting matrix offers a performance mode where Inforiver functions very similar to the native Power BI Matrix by fetching only one hierarchy level at a time. However the flip side is that this disables several features (like custom aggregations) which requires all hierarchy levels.