> For the complete documentation index, see [llms.txt](https://videos.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://videos.inforiver.com/reporting-matrix/general/comparative-measures.md). # Comparative measures Inforiver delivers in-built charting intelligence to manage measures better. Measure management is a feature that is unique to Inforiver. In the earlier versions, the product used 4 separate fields in the Power BI fields pane to capture data – AC, PY, PL and FC. Naturally, many users unfamiliar with IBCS standards had a confusing time assigning fields. Currently, the comparative measure assignment is abstracted into Measure Management which is accessible through the toolbar menu. This ensures that casual users (who constitute more than 90% of Power BI users) do not have to learn about measure assignments or deal with the complexity of managing four different fields. Watch the video to learn more about the multiple use cases that Inforiver covers, listed below: (a) Visualize measures and variances using the IBCS standards in Power BI (b) Split one measure into multiple measures with a time period without using any DAX formula in Power BI (c) Create new measures in Power BI while using DirectQuery (d) Comparison of multiple instances of different measures in Power BI (e) Compare and visualize non-time-based data in Power BI {% embed url="" %} > ## **Related resources** > > #### Blogs > > [The need for better management of comparative measures in Power BI](https://inforiver.com/blog/general/the-need-for-better-management-of-comparative-measures-powerbi/) --- # 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://videos.inforiver.com/reporting-matrix/general/comparative-measures.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.