Forum Discussion
Error creating a table from a dax expression
Hello friends, I'm trying to create a table with the expression dax below, in Dax Studio the expression runs perfectly, but in the power bi desktop it presents an unidentified error. I'm putting Pbix to test so they can help me identify the error.
This expression ran normally and after the version update it stopped scrolling.
Expression running on dax studioExpression running on PBI Desktop
EVALUATE SUMMARIZE( FILTER(TFExecucaoAtendimento, (TFExecucaoAtendimento[SkAceitabilidadeAtendimento]=15) && (TFExecucaoAtendimento[SkPublicoAlvo]=3 ||TFExecucaoAtendimento[SkPublicoAlvo]=4 ||TFExecucaoAtendimento[SkPublicoAlvo]=5) && (TFExecucaoAtendimento[SkSituacaoInstrumento]=2) && (TFExecucaoAtendimento[SkPPA]=201809) ), TFExecucaoAtendimento[SkSebrae], TFExecucaoAtendimento[CodRealizacaoSiac], TFExecucaoAtendimento[SkInstrumento], TFExecucaoAtendimento[SkClientePessoaJuridica], TFExecucaoAtendimento[SkIniciativa], TFExecucaoAtendimento[SkUnidadeOrganizacional_Iniciativa], "CodAtendimento", VAR CodOrigem = VALUES(TDOrigem[CodOrigem]) VAR CodRealSiac = FORMAT(VALUES(TFExecucaoAtendimento[CodRealizacaoSiac]),"GENERAL NUMBER") RETURN CONCATENATE(CodRealSiac,CodOrigem) )
Best Regards
Leudyston Dantas
Hi Leudyston,
I have reported t this issue to the Product Team: CRI 86194073. The workaround is replacing the VALUES with other functions like MIN, MAX, SELECTEDVALUE.
VAR CodOrigem = values(TDOrigem[CodOrigem])
BTW, Do not post sensitive data here.
Best Regards,
Dale
4 Replies
- v-jiascu-msftMicrosoft Employee
Hi Leudyston,
I have reported t this issue to the Product Team: CRI 86194073. The workaround is replacing the VALUES with other functions like MIN, MAX, SELECTEDVALUE.
VAR CodOrigem = values(TDOrigem[CodOrigem])
BTW, Do not post sensitive data here.
Best Regards,
Dale- leudystonHelper I
Hi Dale, thanks for your help.
The PBIX file is no longer available for download.
Best Regards,
Leudyston
- v-jiascu-msftMicrosoft Employee
Hi Leudyston,
The fix is expected in the November release. Thanks for your patience.
Best Regards,
Dale
- v-jiascu-msftMicrosoft Employee
Hi Leudyston,
This issue has been fixed. Thank you for reporting it.
Best Regards,
Dale