Hash-encoded columns that are joined by a relationship should share a dictionary
To save space in the Data Model, 2 columns should share a dictionary if and only if:
- Both columns use hash encoding
- Both columns are joined by a one-to-many relationship
- All values in the column on the "many" side of the relationship can be found in the column on the...
STATUS DETAILSNew
Optimize columns of the same table that have a one-to-one correspondence with each other
If some columns of the same table have a one-to-one correspondence with each other (i.e. for each distinct value of any column, there is only 1 distinct value in the other columns), then they should be optimized to take advantage of that fact. Examples of optimizations:
- All columns ...
STATUS DETAILSNew
Add the missing space in the IntelliSense description of TREATAS
If you type "TREATAS" in a DAX expression and click on the IntelliSense box that appears, the description of TREATAS will appear. It reads:
Treats the columns of the input table as columns from other tables...STATUS DETAILSNew
Revise the IntelliSense description of the PV function
If you type "PV" in a DAX expression and click on the IntelliSense box that appears, the description of PV will appear. It reads:
calculates the present value of a loan or an investment, based on a constant...STATUS DETAILSNew
Improve the security of powerbi.com
Please address the security issues that are identified by Qualys's SSL Server Test:
https://www.ssllabs.com/ssltest/analyze.html?d=powerbi.com
Examples of actions to take include:
- Add support for TLS 1.3
- Drop support for weak cipher suites for TLS 1.2<...
STATUS DETAILSNew
Do not use red underlining for valid DAX code
Red underlining is normally used to indicate an error in a DAX expression, but it also appears for certain types of valid DAX code such as (but not limited to):
- SELECTCOLUMNS when a column is selected without being renamed (e.g. SELECTCOLUMNS('Table','Table'[Column]))
- COLUMN...
STATUS DETAILSNew
Optimize COLUMNSTATISTICS
COLUMNSTATISTICS is a useful but slow function. To make it calculate faster, consider calculating only the portion of it that is used in the DAX expression from which it is called. For example, if I use SELECTCOLUMNS(COLUMNSTATISTICS(),[Table Name]), then only the Table Name column should be c...