Forum Discussion
Table Visual unable to load data despite having fewer rows.
There's way to share no sensitive file? To see closer what causes this loss in performance
It's tough because it has sensitive company data. But for reference this is the video I referred to build the pagination in my table. UX Revolution with Visual Level PAGINATION in Power BI
- SaiK1 year agoHelper I
DEFINE
VAR __DS0FilterTable =
TREATAS({"180 Days"}, 'slicer'[Values])VAR __DS0FilterTable2 =
TREATAS({25}, 'Items'[Items])VAR __DS0FilterTable3 =
TREATAS({1}, 'Pages'[Pages])VAR __ValueFilterDM0 =
FILTER(
KEEPFILTERS(
SUMMARIZECOLUMNS(
'TableB'[Column A],
__DS0FilterTable,
__DS0FilterTable2,
__DS0FilterTable3,
"Measure A", 'Table B'[TMeasure A],"Item_Filter", IGNORE('Table B'[Item Filter])
)
),
[Item_Filter] = 1
)VAR __DS0Core =
SUMMARIZECOLUMNS(
'Table B'[Column A],
__DS0FilterTable,
__DS0FilterTable2,
__DS0FilterTable3,
__ValueFilterDM0,
"Measure A", 'Table B'[Measure A]
)VAR __DS0PrimaryWindowed =
TOPN(501, __DS0Core, [Measure A], 0, 'Table B'[Column A], 1)EVALUATE
__DS0PrimaryWindowedORDER BY
[Measure A] DESC, 'Table B'[Column A] - SaiK1 year agoHelper I
Query (8, 13) A function 'PLACEHOLDER' has been used in a True/False expression that is used as a table filter expression. This is not allowed.
Got this error
- Bibiano_Geraldo1 year agoSuper User
Hi SaiK ,
Please share the generic Dax's used on tha table - Bibiano_Geraldo1 year agoSuper User
Hi SaiK ,
try to update your DAX to look like bellow, this avoid using summirecolumnns twice and improve the perfomance:
DEFINE VAR __FilteredTableB = CALCULATETABLE( 'Table B', TREATAS({"180 Days"}, 'slicer'[Values]), TREATAS({25}, 'Items'[Items]), TREATAS({1}, 'Pages'[Pages]), 'Table B'[Item Filter] = 1 ) VAR __DS0Core = SUMMARIZE( __FilteredTableB, 'Table B'[Column A], "Measure A", 'Table B'[Measure A] ) VAR __DS0PrimaryWindowed = TOPN(501, __DS0Core, [Measure A], DESC, 'Table B'[Column A], ASC) EVALUATE __DS0PrimaryWindowed ORDER BY [Measure A] DESC, 'Table B'[Column A] ASC - Bibiano_Geraldo1 year agoSuper User
Sorry about that, use filter instead:
DEFINE VAR __FilteredTableB = CALCULATETABLE( 'Table B', TREATAS({"180 Days"}, 'slicer'[Values]), TREATAS({25}, 'Items'[Items]), TREATAS({1}, 'Pages'[Pages]), FILTER('Table B', 'Table B'[Item Filter] = 1) // ✅ Fixed filter ) VAR __DS0Core = SUMMARIZE( __FilteredTableB, 'Table B'[Column A], "Measure A", 'Table B'[Measure A] ) VAR __DS0PrimaryWindowed = TOPN(501, __DS0Core, [Measure A], DESC, 'Table B'[Column A], ASC) EVALUATE __DS0PrimaryWindowed ORDER BY [Measure A] DESC, 'Table B'[Column A] ASC - SaiK1 year agoHelper I
Resource Governing: This query uses more memory than the configured limit. The query — or calculations referenced by it — might be too memory-intensive to run. Either reach out to your Analysis Services server administrator to increase the per-query memory limit or optimize the query so it consumes less memory. More details: consumed memory 1024 MB, memory limit 1024 MB.