![]() For example, let’s say I want to have end users drill down from category to subcategory. In the Power BI Desktop app, creating a hierarchy is fairly simple. To start out, let’s make sure we understand the components of a hierarchy that we will need to replicate using our TOM script. Please reference the DataOnWheels GitHub page for sample PBIX files and C# packages, but note you will need a Power BI Premium workspace with XMLA endpoint write-back enabled in order to run this entire demo. If you are new to using C# and the Tabular Object Model (TOM), please check out the previous blog post ( ) for both an introduction to the topic and detailed instructions on getting the C# portion of this demo stood up. Unfortunately, while we can manipulate, add, and delete hierarchies and their levels, visuals already containing the hierarchy will not be automatically adjusted with any new levels/ordinals. NET applications to dynamically add or remove levels from hierarchies as they are created/removed in your application. Thankfully, if you have Power BI premium you can use the XMLA endpoint to add code into existing. While hierarchies can be a useful resource for self-serve analytics, maintaining hierarchies can be a pain as new levels get added or removed. Power BI hierarchies are a powerful and easy way to enable end users to dig deeper into their visuals and data. My previous posts have covered code around adding, deleting, and adjusting columns and measures, but this one will address how to manipulate hierarchies. Quick refresher, the Tabular Object Model can be accessed through the XMLA endpoint in Power BI Premium workspaces. This post is a continuation of my adventure into the Tabular Object Model and how we can use it to make Power BI scalable and incorporate it into existing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |