> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/resources/plan-preview-frequently-asked-questions/multi-dimensional-planning.md). # Multi-dimensional planning This FAQ addresses common questions that may arise while working with multidimensional planning in Fabric. It covers the reasoning behind Cube measures, how multidimensional allocation works, and bidirectional sync behavior. ### What is a Cube measure, and how is it different from a regular measure? A regular measure pulls a value directly from the semantic model or a planning sheet at whatever granularity it exists. A Cube measure is a calculated allocation layer — it takes a measure with limited granularity and distributes it across additional dimensions using a reference measure as the basis for distribution, without altering the source data. ### Can I add more than one breakdown to the same Cube measure? Yes - you can add multiple breakdowns, which are useful when you need to segregate planning into groups such as geography, category, or customer type. However, all breakdowns must have a common dimension. ### If I create a data input cube measure using the Copy from another series option, and the base measure is later updated, does the cube measure change too? No — the base measure only populates the cube measure at the point when it is created. After that, the cube measure becomes its own independent editable series. A later change to the base measure would not retroactively update the cube — the two are no longer linked once the copy is made. ### What would happen if you tried to pull a cube measure into another sheet using From Sheets instead of Cube Measures? The values would not populate. Without the Cube breakdown, Infobridge has no way to resolve the measure at the additional dimensions — it can only read the measure at the grain at which it was created. This is the core problem Cube Measures solves. ### When a subtotal value is updated, why do individual category combinations under the subtotal value update too? The update is applied to the subtotal, and the cube breakdown distributes that change proportionally down to every dimension category combination under the subtotal, based on their share of the reference measure. ### Why do I need to use the Insert as measure option to import cubes, rather than pull in the same way other referenced measures are? Inserting it specifically as a Cube measure is what preserves its two-way behavior. If it were pulled in as a regular read-only reference, the consuming sheet would only display the value — it can't be edited there. Inserting it through Cube Measures keeps the breakdown-based link intact, so an edit on the consumer flows back to the origin just as an edit on the origin flows forward to the consumer. --- # 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.fabricplan.com/resources/plan-preview-frequently-asked-questions/multi-dimensional-planning.md?ask=&goal= ``` `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.