Forum Discussion
Error When Using Power Query to Restrict Data
- 4 years ago
Hello v-janeyg-msft,
It works now. The error refers to the calmonth field which is numeric and there is no null value for that field so it is odd when it refers to such error.
What I did was, I used August release (because latest release has a bug and I can't refresh). Then I select the field and choose 'keep errors'. It will generate a new step.
#"Filtered Rows" = Table.SelectRows(Table,
each ([calmonth] = List.Max(Table[calmonth]) or [calmonth] = List.Max(Table[calmonth])-1)),
#"Kept Errors" = Table.SelectRowsWithErrors(#"Filtered Rows")
in
#"Kept Errors"Then I 'apply' and it got refreshed. The first refresh was successful but the table was empty, so I tried few times until it gets populated.
After that I removed the ‘keep errors’ option and refresh again. Seems like it works fine now.
Mimi_Ibrahim , Either you are getting a null as max or you are getting non-numeric value for calmonth, please check that
Thank you amitchandak. I have checked that the format for the calmonth is numerical in Cloudera and it is the same in 'Transform Data'. I didn't do any change to the field type, the data just loads directly from the source table and it failed with the mentioned error.
Funny that only myself is having the error, not my other colleagues. Is there a setting that I need to change in my PBI desktop? I'm currently using August PBI release. Appreciate if you could advise, thank you.