High Max penalty −15 pts Medium Max penalty −8 pts Low Max penalty −4 pts

Modeling

Semantic model structure - schema, relationships, types, tables
25 %
of global score
Rule Description Severity Recommendation
MOD001Snowflake schema - dimension linked to another dimension (snowflake)HighFlatten nested dimensions to obtain a pure star schema. Snowflake schemas increase DAX query complexity and degrade VertiPaq performance.
MOD002Fact tables not identifiable in the modelMediumEnsure your fact tables are recognized as such: they must be on the N side of a relationship with at least one dimension table.
MOD003No dedicated date table presentHighCreate a dedicated date table and mark it as such. DAX time intelligence only works correctly with a well-configured date table.
MOD004Date table present but not marked IsDateTableMediumMark your date table via the "Mark as date table" option in Power BI Desktop. This activates VertiPaq optimization and DAX time intelligence validations.
MOD005Uncontrolled many-to-many relationship detectedHighM:N relationships are rarely desirable. Introduce a junction table or review the modeling to switch to classic 1:N relationships.
MOD006Bidirectional relationships without apparent justificationMediumBidirectional filters can cause unexpected behavior and degrade performance. Use CROSSFILTER() in DAX if bidirectional filtering is only needed in certain measures.
MOD007Inactive relationships present without use of USERELATIONSHIP()LowUnused inactive relationships clutter the model. Delete them if they are not activated by any measure via USERELATIONSHIP().
MOD008Isolated tables - not linked to the rest of the modelMediumEach table must be linked to the model via at least one active relationship. Isolated tables cannot filter other tables and are often a sign of modeling errors.
MOD009Foreign keys not hidden in fact tablesLowForeign key columns (ID) in fact tables should be hidden in the report view. They are only useful for relationships and have no direct analytical value.
MOD010Date columns with incorrect data type (not Date or DateTime)MediumDate columns must have the Date or DateTime type. A Text or Integer type prevents time intelligence functions and degrades filtering performance.
MOD011Calculated columns present in a fact tableHighCalculated columns in fact tables are evaluated at each refresh and stored in memory column by column. Move these calculations to Power Query or the SQL source.
MOD012No dedicated measure tableLowGroup all your measures into one or more dedicated tables (without data). This significantly improves model readability and navigation for end users.
MOD013Calculated tables that could be replaced by M transformationsMediumDAX calculated tables are fully recalculated at each refresh. Prefer Power Query (M) transformations for static derived tables - they do not consume DAX engine memory.
MOD015Unused columns not hidden in the report viewLowColumns not used in visuals, measures, or relationships should be hidden (or deleted) to lighten the model and simplify the end-user experience.
MOD016Primary key not identifiable in dimension tablesLowEach dimension must have a column identified as the primary key (1 side of the relationship) to ensure referential integrity and allow Power BI to optimize joins.
MOD017Excessive number of columns in a fact table (configurable threshold)MediumWide fact tables (many columns) degrade VertiPaq performance. Review the necessity of each column - descriptive attributes belong in dimensions, not facts.
MOD018Primary key column (side 1) not hidden in a dimensionLowThe side 1 key column of a relationship can be hidden if it has no direct use in reports. It remains functional for relationships even when hidden.
MOD019Suspect table - present on both side 1 and side N of relationshipsMediumA table that is both on the N and 1 side of different relationships is often a sign of hybrid modeling to be reviewed. Check if this is an intentional choice and document it.
MOD020Auto date/time enabled - LocalDateTable detectedHighThe auto date/time feature generates hidden date tables for each date column, significantly increasing model size. Disable it and use your own date table.
MOD021Fact → Fact relationship detectedHighDirect relationships between fact tables are a classic modeling error. Introduce a shared dimension table (degenerate dimension or bridge dimension) to link your fact tables.
MOD022One-to-one (1:1) relationship detectedMedium1:1 relationships often indicate two tables that should be merged. Check if this separation is intentional or a migration artifact.
MOD023Snowflake schema - dimension linked to other dimensions (cascade)HighSimilar to MOD001 but for deep dimension cascades. Flatten the hierarchy to return to a star schema. Use Power Query to denormalize if necessary.
MOD024Do not use floating point data typesMediumReplace the Double type with Decimal for monetary or financial values, or with Int64 for integers. The Double type should only be used for scientific calculations where absolute precision is not required.
MOD025Set data coverage definition on DirectQuery partition of hybrid tableMediumDefine a DataCoverageDefinition expression on the DirectQuery partition to tell the engine the data range covered by the Import partition.
MOD026Dual mode irrelevant without DirectQueryMediumConvert Dual partitions to Import if the model is purely in Import mode, or add a DirectQuery source if Dual mode is intentional.
MOD027Set dimension tables to Dual mode when using DirectQuery on fact tablesMediumSwitch Import dimension tables to Dual mode when the model contains hybrid tables. This allows the engine to use in-memory data or send the query to the source depending on the context.
MOD028Do not summarize numeric columnsMediumSet SummarizeBy = 'None' on all visible numeric columns and create explicit DAX measures for all required aggregations.
MOD029Add data category for geographic columnsLowSet the DataCategory property on the column to the appropriate geographic value (Country, City, Continent, Latitude, Longitude) in Power BI Desktop.
MOD030Percentages should be formatted correctlyMediumUse the standard format '#,0.0%;-#,0.0%;#,0.0%' for all percentage measures to ensure consistent display of positive, negative, and zero values.
MOD031Calculation items must have an expressionHighDefine a valid DAX expression on all Calculation Items. If the Calculation Item is no longer needed, remove it from the Calculation Group.
MOD032Data columns must have a source columnHighCheck the column definition in Power Query and ensure the SourceColumn property points to a valid column in the data source.

DAX

Static analysis of DAX measures - patterns, practices, dependencies
25 %
of global score
RuleDescriptionSeverityRecommendation
DAX001Use of FILTER(ALL(...))HighReplace FILTER(ALL(Table), condition) with CALCULATETABLE(ALL(Table), condition) or restructure the filter in CALCULATE() directly.
DAX002Nested iterators (SUMX, AVERAGEX… in another iterator)HighRefactor with variables or intermediate tables to reduce the cardinality of evaluation contexts.
DAX003Division without DIVIDE()MediumReplace A / B with DIVIDE(A, B) to automatically handle divisions by zero without raising an error.
DAX004Use of COUNTROWS(FILTER(...))HighReplace with CALCULATE(COUNTROWS(Table), condition). The version with FILTER iterates all rows; the CALCULATE version relies on the VertiPaq index.
DAX005IF() without explicit ELSE branchLowAn IF() without ELSE implicitly returns BLANK(). Make the return explicit to avoid unexpected behavior in totals.
DAX006Variables declared but not used in the measureLowDelete unused variables.
DAX007Empty measure - empty body or containing only a commentMediumDelete empty measures or complete their implementation.
DAX008Use of IFERROR()MediumPrefer DIVIDE() for divisions and handle errors at the source in Power Query.
DAX009Nested CALCULATE()MediumRefactor by combining filter modifiers into a single CALCULATE().
DAX010Time intelligence functions used without marked date tableHighFunctions like TOTALYTD() and SAMEPERIODLASTYEAR() require a table marked as IsDateTable.
DAX011Reference to a column without aggregation in a measureHighAlways add an aggregation function (SUM, MAX, etc.) to avoid errors outside of row context.
DAX012Excessive dependency depth between measuresMediumFlatten the hierarchy or group intermediate calculations to make debugging easier.
DAX013Use of RELATED() in cascade across multiple tablesMediumConsider denormalizing the column directly in Power Query.
DAX014Implicit measures present with calculation groupsHighConvert all aggregations into explicit measures when using Calculation Groups.
DAX015Calculation group items without descriptionLowAdd a description to each Calculation Item for end users.
DAX016CONCATENATEX() on a large tableHighLimit its use to small reference tables to avoid extreme slowness.
DAX017SUMMARIZE() with extension columnsMediumUse ADDCOLUMNS(SUMMARIZE(...)) instead.
DAX018ADDCOLUMNS() without CALCULATE() on expressionsMediumUse CALCULATE() to transition row context into filter context.
DAX019Use TREATAS instead of INTERSECTMediumReplace INTERSECT(...) with TREATAS(table, column1, column2, ...) when the goal is to propagate a filter across tables.
DAX020EVALUATEANDLOG not in productionMediumRemove EVALUATEANDLOG() from all measures before going to production. This function is reserved for local debugging.
DAX021Measure is a direct reference to another measureMediumRemove the redundant measure and use [OtherMeasure] directly where it is referenced.
DAX022No two measures should have the same definitionMediumRemove the duplicate measure and keep a single version.
DAX023Avoid constant addition to division resultMediumReview the calculation logic. If an offset is intentional, encapsulate it in a VAR variable to make the intent explicit.
DAX024Avoid 1-(x/y) syntax, use 1 - DIVIDE(x, y)MediumReplace the '1 - x/y' pattern with '1 - DIVIDE(x, y)' to benefit from division-by-zero protection.
DAX025Filter column values with proper syntaxMediumReplace CALCULATE([Measure], FILTER('Table', 'Table'[Column] = value)) with CALCULATE([Measure], 'Table'[Column] = value) when the filter targets a single column.
DAX026Column references should be fully qualifiedHighAlways qualify column references with their table name: 'Table'[Column] or Table[Column].
DAX027Measure references should be unqualifiedHighReplace 'Table'[MyMeasure] with [MyMeasure] in all DAX expressions.
DAX028Avoid SUM or AVERAGE on a string columnHighCheck the data type of the referenced column. Convert to a numeric type or use COUNTROWS / DISTINCTCOUNT as appropriate.
DAX029Inactive relationships never activatedMediumCheck whether the inactive relationship is intentional. If it is never used, remove it.
DAX030Calculation groups with no calculation itemsMediumEither complete the Calculation Group by adding items, or delete the table.

Governance

Documentation, naming conventions, RLS security
3 %
of global score
RuleDescriptionSeverityRecommendation
GOV001Model description missingLowAdd a global description to the semantic model explaining its purpose and scope.
GOV002Tables without descriptionLowDocument each table with a description indicating its content and granularity.
GOV003Columns without descriptionLowDocument key columns, especially those exposed to end users.
GOV004Generic names detected (e.g., Column1, Table2)MediumRename objects with explicit business names.
GOV005Measure naming convention not respectedLowAdopt a uniform convention (e.g., [Total Sales]) and apply it to all measures.
GOV006Table naming convention not respectedLowStandardize table names with a clear prefix (e.g., dim_, fct_).
GOV007No RLS role present on a model with sensitive dataHighImplement row-level security (RLS) as soon as the model contains restricted data.
GOV008RLS role with empty filterHighAn RLS role with an empty filter or TRUE() grants access to all data. Correct this immediately.
GOV009Unbalanced parentheses in RLS filter expressionHighCheck and correct the DAX syntax of the role expression.
GOV010RLS roles without descriptionLowDocument each RLS role: targeted users and restricted data scopes.
GOV011KPI measures without status indicator or target definedLowComplete KPI definitions with a target value and status thresholds.
GOV012Measures exposed to users without descriptionMediumVisible measures must have a description explaining their calculation and unit.
GOV013Measures without defined FormatStringLowDefine a display format (currency, percentage, etc.) for each measure.
GOV014Generic column nameMediumRename the column with an explicit business name.
GOV015Generic measure nameMediumRename the measure with an explicit business name.
GOV016Check if dynamic RLS is necessaryLowVerify that dynamic RLS is actually needed. Consider static RLS for small, stable user groups.
GOV017Limit RLS logic complexityMediumSimplify the RLS filter by pre-calculating values in a dedicated column.
GOV018Objects should not start or end with a spaceHighRename the object by removing leading and trailing spaces.
GOV019First letter of objects must be capitalizedLowRename the object by capitalizing the first letter for consistent readability.
GOV020Object names must not contain special charactersMediumRemove invisible control characters (tabs, carriage returns, newlines) from names.
GOV021Mark primary key columnsLowEnable the IsKey property on all columns on the 'One' side of relationships in dimension tables.

VertiPaq

Columnar storage engine - memory, compression, partitions
20 %
of global score
RuleDescriptionSeverityRecommendation
VPQ001High cardinality columns detectedHighHide or delete high cardinality columns if they are not used in visuals or measures.
VPQ002Insufficient compression ratio on some columnsMediumEvaluate if the column is necessary and optimize its data type.
VPQ003Hash encoding where Value encoding would be more efficientMediumCheck that your numeric columns have the correct data type (Integer vs Decimal).
VPQ004Unused columns not deleted from the modelHighDelete columns not used in any visual, measure, or relationship.
VPQ005Excessive total model sizeHighAnalyze the heaviest tables and optimize column by column.
VPQ006Fact tables with too many columnsMediumReduce the number of columns by moving attributes into dimension tables.
VPQ007Too low ratio of useful data vs total volumeMediumEliminate unnecessary columns or tables.
VPQ008Large tables not partitionedHighImplement partitioning by date to allow incremental refreshes.
VPQ009Disproportionate partition sizesMediumRebalance partitions to optimize parallelism during refreshes.
VPQ010Empty partitions detectedLowDelete or merge empty partitions.
VPQ011Incremental refresh missing on large tablesHighConfigure incremental refresh for all tables exceeding the critical size threshold.
VPQ012High referential integrity violationsHighClean data at the source to guarantee referential integrity.
VPQ013Excessive number of segments per columnMediumCheck the data type and cardinality of the column.
VPQ014Tables with columns not resident in memory (DirectLake)MediumForce residency for frequently queried columns to avoid falling back to DirectQuery.

Performance

Actual execution of DAX measures with XMLA trace analysis
15 %
of global score
RuleDescriptionSeverityRecommendation
PER001 Slow DAX measure - total FE + SE duration exceeds configured threshold (default: 1,000 ms) High / Medium Simplify the measure, add variables, and reduce the cardinality of involved columns.

Power Query

Analysis of M queries - transformations foldable to SQL source
12 %
of global score
Rules PQY001 to PQY008 apply only to queries where the source is a SQL database. PQY009 applies to non-SQL sources.
RuleDescriptionSeverityRecommendation
PQY001Join performed in Power Query (Merge) on a SQL sourceHighPerform joins directly in SQL at the source (JOIN clause).
PQY002Reference to another Power Query query (Reference)HighVerify if query folding is maintained; otherwise, refactor into a single SQL query.
PQY003Sort performed in Power Query (Table.Sort) on a SQL sourceHighMove the sorting to the SQL query (ORDER BY).
PQY004Column selection in Power Query (Table.SelectColumns) on a SQL sourceHighSelect only necessary columns directly in the SQL query.
PQY005Grouping performed in Power Query (Table.Group) on a SQL sourceHighPerform the grouping in SQL (GROUP BY).
PQY006Adding calculated column in Power Query (Table.AddColumn) on a SQL sourceHighAdd the calculated column directly in the SQL query or a view.
PQY007Nested join in Power Query (Table.NestedJoin) on a SQL sourceHighReplace with LEFT JOINs in your source SQL query.
PQY008Use of Navigate to access a table in a SQL sourceHighDefine the SQL query directly in the Source step (Value.NativeQuery).
PQY009Non-SQL data source detected for high data volumeMediumMigrate to a relational database (SQL Server, PostgreSQL, etc.) for better performance.
PQY010The number of steps in the M query exceeds the configured threshold (default: 10).HighA high number of M steps increases the risk of slow refreshes and excessive Capacity Unit consumption on large volumes. Simplify the query or push transformations back to the source.
PQY011Use of Table.Unpivot or Table.Pivot detected in the Power Query query.MediumThese functions consume significant resources during refreshes, especially on large data volumes, which can considerably increase the Capacity Unit consumption of Data Refresh operations on the Fabric capacity. Consider restructuring the table at the source or limiting the volume processed.
PQY012Use of SharePoint.Files detected in the Power Query query.HighSharePoint.Files performs a recursive search across the entire SharePoint site, which is costly in terms of performance. Use SharePoint.Contents to extract files located in a specific folder or location, and reserve SharePoint.Files for cases where a genuine site-wide search is required.