Using a card as a slicer in Power BI is a common question I receive. The quick answer is it is not possible - I hear this much too often from others. However, that is a very rare statement I would make about Power BI. It is a rare statement
Power BI Dashboard Filters sometimes cause confusion.
In one of my many communication channels, there was a question posed related to the ability to add Power BI dashboard filters in order to filter Power BI dashboard tiles. There is some confusion at times and I would like to make a short article
Power Pivot or SSAS Tabular data model optimization is important for Power View reporting usability and functionality.
In this posting, we will discuss the following topics:
X-Axis Guidelines
Advanced Properties
Image Handling
Data Categories
Table Behavior
Field Behavior
X-Axis Guidelines
Data type and distribution
Utilize a number or date that increases uniformly (primarily for Power BI forecasting but we have
Before a Power View report can be built, you have to have a data model built as a data source. There are several configuration options to help optimize your data model specifically for Power View. These configurations and/or optimizations are made within your Power Pivot model or in SQL Server
DAX Best Practices
are vital when utilizing large data models and looking to improve performance. You can get away with poor practices on small models but you will see performance issues as your data grows.
Data Analysis Expressions (DAX)
is the native query and formula language for Microsoft Power Pivot data models and SQL
Power View is an interactive data exploration, visualization, and presentation experience that encourages intuitive ad-hoc reporting. It is a feature of Microsoft Excel 2013, and of Microsoft SharePoint Server 2010 and 2013 Enterprise Edition.
Power View in SharePoint is browser-based Silverlight application, a feature of the SQL Server Reporting Services Add-in for Microsoft
Organization and user friendly data model development in Power Pivot & Tabular environments take precedence over almost all other concerns.
We will discuss best practices of creating a data dictionary, naming rules, etc. of Power Pivot & Tabular data models in other, related postings.
In this posting, we will discuss some options of organizing the
Normalization vs. Denormalization best practices for Power Pivot / Tabular data modeling is typically not disputed.
First, let's quickly define in human terms what we are referencing when we speak of normalization vs. denormalization. Normalization is reducing data duplication by splitting dimensional data and attributes into their dimension tables. Typically,
We will start off discussing the data model itself.
The data model that is created in Power Pivot or a Tabular solution is the foundation of any Microsoft business intelligence solution.
The data model consists of the data structure (including tables and their relationships, columns in the tables, and all measures
We have seen several dispersed articles on Power Pivot, SSAS Tabular, and Data Analysis Expressions (DAX) best practices.
Over many articles, we will attempt to consolidate many of these into a single, consolidated location as well as adding new material to the list based on our experiences as well as any
