Skip to content

Changed BPA/failureMode #2

Changed BPA/failureMode

Changed BPA/failureMode #2

Triggered via push May 7, 2024 16:36
Status Success
Total duration 53s
Artifacts
Deployment
42s

Annotations

3 errors, 7 warnings, and 7 notices
[DAX Expressions] Measure references should be unqualified
Using unqualified measure references makes it easier to distinguish between column and measure references, and also helps avoid certain errors. When referencing a measure using DAX, do not specify the table name. Use only the measure name in square brackets.
[Formatting] Provide format string for measures
Visible measures should have their format string property assigned
[Formatting] Do not summarize numeric columns
Numeric columns (integer, decimal, double) should have their SummarizeBy property set to "None" to avoid accidental summation in Power BI (create measures instead).
Deployment
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
[Performance] Set IsAvailableInMdx to false on non-attribute columns
To speed up processing time and conserve memory after processing, attribute hierarchies should not be built for columns that are never used for slicing by MDX clients. In other words, all hidden columns that are not used as a Sort By Column or referenced in user hierarchies should have their IsAvailableInMdx property set to false.
[Performance] Minimize Power Query transformations
Minimize Power Query transformations in order to improve model processing performance. It is a best practice to offload these transformations to the data warehouse if possible. Also, please check whether query folding is occurring within your model. Please reference the article below for more information on query folding.
[Performance] Reduce usage of calculated tables
Migrate calculated table logic to your data warehouse. Reliance on calculated tables will lead to technical debt and potential misalignments if you have multiple models on your platform.
[Performance] Remove redundant columns in related tables
Removing unnecessary columns reduces model size and speeds up data loading.
[Maintenance] Remove unnecessary columns
Hidden columns that are not referenced by any DAX expressions, relationships, hierarchy levels or Sort By-properties should be removed.
[Formatting] Hide foreign keys
Foreign keys should always be hidden.
[Maintenance] Remove roles with no members
May remove roles with no members.
[Maintenance] Ensure tables have relationships
This rule highlights tables which are not connected to any other table in the model with a relationship.
[Maintenance] Visible objects with no description
Add descriptions to objects. These descriptions are shown on hover within the Field List in Power BI Desktop. Additionally, you can leverage these descriptions to create an automated data dictionary (see link below).
[Naming Conventions] Partition name should match table name for single partition tables
Tables with just one partition should match their table and partition names.Tables with more than one partition should have each partition name starting with the table name.
[Formatting] Provide format string for "Date" columns
Columns of type "DateTime" that have "Month" in their names should be formatted as "mm/dd/yyyy".
[Formatting] Provide format string for "Month" columns
Columns of type "DateTime" that have "Month" in their names should be formatted as "MMMM yyyy".
[Formatting] Relationship columns should be of integer data type
It is a best practice for relationship columns to be of integer data type. This applies not only to data warehousing but data modeling as well.