The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Dear all.
I'm importing tables from Power BI to Excel but I don´t know why I'm obtaining the next error:
I've done:
But no way. Do you know why?
The DAX makes little sense. You are summarizing by columns that you are also aggregating, specifically Orden and Orden2. Why would you do that?
Hi @Luis_Caston ,
I agree with your point. When the number of bytes exceeds a threshold, it may cause this error.
I found a similar post.
Hope it helps.
Best Regards,
Wearsky
Hi @Luis_Caston ,
I cannot reproduce the issue. Could you please check these prerequisites?
Best Regards,
Wearsky
Hi!
Yes, my verion is over:
Are you trying to do this from within DAX Studio?
Hi!
I've tryed from all...
I've been able to charge the table on this way but I think the problem comes from the resources, that is to say, the table has columns with calculated fields I think that consumes all the resources and stops.
I don´t know exactly the bytes but I've tryed removing two columns and have charged the rest of the table.
Are you sure it's the columns? Your Excel file can have 16K columns (not saying that it should, but that's your limit). Maybe the query returns too many rows, beyond 1 million?
Hi!
Yes is due to the columns and rows are 500 more or less (a few).
Removing this tree works:
Besides I've tried adding only this three alones and have 300 rows.
Checking the connection I've two "identical" tables one in Spanish and another one in English.
This is the code of the connection at Excel of the English table where I've problems:
DEFINE
VAR __DS0Core =
SUMMARIZECOLUMNS(
'dim_pyg_analitica_ingles'[NumFila1],
'dim_pyg_analitica_ingles'[Nivel1],
'dim_pyg_analitica_ingles'[NumFila2],
'dim_pyg_analitica_ingles'[Nivel2],
'dim_pyg_analitica_ingles'[Orden2],
'dim_pyg_analitica_ingles'[NumFila3],
'dim_pyg_analitica_ingles'[Nivel3],
'dim_pyg_analitica_ingles'[NumFilaX],
'dim_pyg_analitica_ingles'[NivelXEsquema],
'dim_pyg_analitica_ingles'[Esquema],
'dim_pyg_analitica_ingles'[CodCuenta-Descripción],
'dim_pyg_analitica_ingles'[CodCuenta],
'dim_pyg_analitica_ingles'[Level2],
'dim_pyg_analitica_ingles'[Level3],
'dim_pyg_analitica_ingles'[Level4],
'dim_pyg_analitica_ingles'[Level5],
'dim_pyg_analitica_ingles'[Level6],
'dim_pyg_analitica_ingles'[OrdenOK],
'dim_pyg_analitica_ingles'[Nivel3OK],
'dim_pyg_analitica_ingles'[Orden],
'dim_pyg_analitica_ingles'[Clasificación],
'dim_pyg_analitica_ingles'[Custom],
"SumOrden1", CALCULATE(SUM('dim_pyg_analitica_ingles'[Orden1])),
"SumOrden2", CALCULATE(SUM('dim_pyg_analitica_ingles'[Orden2])),
"SumOrden3", CALCULATE(SUM('dim_pyg_analitica_ingles'[Orden3])),
"SumOrdenX", CALCULATE(SUM('dim_pyg_analitica_ingles'[OrdenX])),
"SumSigno", CALCULATE(SUM('dim_pyg_analitica_ingles'[Signo])),
"SumOrden", CALCULATE(SUM('dim_pyg_analitica_ingles'[Orden]))
)
VAR __DS0BodyLimited =
TOPN(
500000,
__DS0Core,
'dim_pyg_analitica_ingles'[NumFila1],
1,
'dim_pyg_analitica_ingles'[Nivel1],
1,
'dim_pyg_analitica_ingles'[NumFila2],
1,
'dim_pyg_analitica_ingles'[Orden2],
1,
'dim_pyg_analitica_ingles'[Nivel2],
1,
'dim_pyg_analitica_ingles'[NumFila3],
1,
'dim_pyg_analitica_ingles'[Nivel3],
1,
'dim_pyg_analitica_ingles'[NumFilaX],
1,
'dim_pyg_analitica_ingles'[NivelXEsquema],
1,
'dim_pyg_analitica_ingles'[Esquema],
1,
'dim_pyg_analitica_ingles'[CodCuenta-Descripción],
1,
'dim_pyg_analitica_ingles'[CodCuenta],
1,
'dim_pyg_analitica_ingles'[Level2],
1,
'dim_pyg_analitica_ingles'[Level3],
1,
'dim_pyg_analitica_ingles'[Level4],
1,
'dim_pyg_analitica_ingles'[Level5],
1,
'dim_pyg_analitica_ingles'[Level6],
1,
'dim_pyg_analitica_ingles'[OrdenOK],
1,
'dim_pyg_analitica_ingles'[Orden],
1,
'dim_pyg_analitica_ingles'[Nivel3OK],
1,
'dim_pyg_analitica_ingles'[Clasificación],
1,
'dim_pyg_analitica_ingles'[Custom],
1
)
EVALUATE
__DS0BodyLimited
ORDER BY
'dim_pyg_analitica_ingles'[NumFila1],
'dim_pyg_analitica_ingles'[Nivel1],
'dim_pyg_analitica_ingles'[NumFila2],
'dim_pyg_analitica_ingles'[Orden2],
'dim_pyg_analitica_ingles'[Nivel2],
'dim_pyg_analitica_ingles'[NumFila3],
'dim_pyg_analitica_ingles'[Nivel3],
'dim_pyg_analitica_ingles'[NumFilaX],
'dim_pyg_analitica_ingles'[NivelXEsquema],
'dim_pyg_analitica_ingles'[Esquema],
'dim_pyg_analitica_ingles'[CodCuenta-Descripción],
'dim_pyg_analitica_ingles'[CodCuenta],
'dim_pyg_analitica_ingles'[Level2],
'dim_pyg_analitica_ingles'[Level3],
'dim_pyg_analitica_ingles'[Level4],
'dim_pyg_analitica_ingles'[Level5],
'dim_pyg_analitica_ingles'[Level6],
'dim_pyg_analitica_ingles'[OrdenOK],
'dim_pyg_analitica_ingles'[Orden],
'dim_pyg_analitica_ingles'[Nivel3OK],
'dim_pyg_analitica_ingles'[Clasificación],
'dim_pyg_analitica_ingles'[Custom]
Then only difference with the Spanish table that charges withoutp problems are those columns:
Sum of the top and the cheks orden.
I think those columns are collapsing the query.
User | Count |
---|---|
74 | |
70 | |
39 | |
30 | |
28 |
User | Count |
---|---|
104 | |
95 | |
51 | |
48 | |
46 |