coalesce
4 TopicsMay 2020 RS New DAX Function COALESCE doesn't work
I was excited to see when we upgraded to the May 2020 version that we can finally use coalesce as a dax function. I loaded it right in tabular and deployed. Doesn't work. "Failed to resolve name COALESCE" even though SSAS tabular model correctly calculates it before deployment. A friend said oh no it works inside of Power BI, ummm ok let me try that. I typed in a new measure: TESTMeasure = COALESCE (1,2) and immediately I see the red squiggly lines of terror. When I hover over them it says Cannot find name 'COALESCE' and 'COALESCE' is not a function. So what happened to the May 2020 new features (Power BI Report Server May 2020 Feature Summary | Microsoft Power BI Blog | Microsoft Power BI)? Ed WatsonSolved4.9KViews0likes8CommentsCoalesce replace Blank
For showing the count which replaces the Blank to 0 at the cart, I have been using the following dax query: Cases = var caseCount = DISTINCTCOUNT(DD_FLU_DEMOGRAPHIC[Case ID]) return IF(ISBLANK(caseCount), 0, caseCount) But the problem is it rounds up the count. For example, it shows 38560 as 40K. Would you please suggest any alternative? I tried with coalesce function but it does not work for the string type data (for example, Case ID ) Regards1.4KViews0likes2CommentsCan a scalar measure increase the row count of a table visual that is based on a single table?
This one has me scratching my head. I always thought that scalar measures can only be an additional attribute to an existing physical row of data, or contribute to the aggregations. However below is a case where adding a measure to a table visual will increase the number of rows displayed in the visual. Data Source SoC: let Source = Table.FromRows(Json.Document(Binary.Decompress(Binary.FromText("i45W8srPyFPSUUJGRkqxOnAJx7yUotRyZGlDrNK+iUWVBEyAKvFKzE0tJkGdV35xBpAyIEatR2piSUZqEUHlpcUlmXnEuAGm0CsxL7WEaGN9M5MzUnNyUtE1ANVlg/SlJOZiD05UBQGpJWC/4DImLz01JxG/QTAlYKcmws2KBQA=", BinaryEncoding.Base64), Compression.Deflate)), let _t = ((type nullable text) meta [Serialized.Text = true]) in type table [H1 = _t, H2 = _t, H3 = _t, H4 = _t, H5 = _t, #"Span of control" = _t]) in Source Table visual: Measure: SOC2 = Coalesce(CALCULATE(DISTINCTCOUNT(SoC[H5]),SoC[H5]<>""),CALCULATE(DISTINCTCOUNT(SoC[H4]),SoC[H4]<>"")) (the measure is not finished, but that's besides the point - I think) Adding the measure as a table visual value gives: What would be the explanation for this behavior?2.5KViews2likes6Comments