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 calculated. If I use FILTER(COLUMNSTATISTICS(),[Table Name]="Table1"), then the statistics columns of COLUMNSTATISTICS should be calculated only for the columns of Table1. This is in contrast to calculating all of COLUMNSTATISTICS and then filtering the result to show only the rows for Table1.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
**BUG** Please fix web model editor UI not working with role-playing dimensions
A key part of complex semantic models is the ability to reuse tables for scenarios like role-playing dimensions (e.g., Date table for DOB, Date table for SalesDate). I've specifically run into this w...arpost3 hours agoPost ProdigyNew4Views0likes0Comments- fbcideas_migusr3 hours agoNew MemberNew326Views10likes3Comments
Favorites, recent fields and field groups in the Data pane (large models)
On big models the Data pane is a pain. Search helps, but you keep searching the same stuff again and again. And when a lot of fields have almost the same name (UN, UN METAS, UN_corr, UNIDAD_NEGOCIO…)...WildAnalyst3 hours agoNew MemberNew4Views1like0Comments