I have attached a PBIX illustrating the issue.
The issue:
Under certain conditions, measures that return a text value will return incorrect results when a calculation group exists in the model (even if the calculation group is not applied).
Sample PBIX:
The problem measure is Stars UNICHAR 11088 (error).
The measure definition is:
Stars UNICHAR 11088 (error) =
VAR SingleStar =
UNICHAR ( 11088 ) -- Star character 11088 "⭐"
VAR NumStars =
[Selected Company]
VAR Result =
REPT ( SingleStar, NumStars )
RETURN
Result
This measure is intended to return a text value containing Unicode character 11088 repeated [Selected Company] times, where
Selected Company =
SELECTEDVALUE ( Company[Company ID] )
The model includes a calculation group with a single calculation item with expression
SELECTEDVALUE () & ""
This calculation group is not applied in the report, however.
Behaviour:
- In a table visual including Company ID and [Star UNICHAR 1108 (error)] (plus some other measures) with no filters applied, the measure always returns a single star.
- When Company ID is filtered on a single value, the measure returns expected results.

- The issue can be resolved by including an additional character in the repeated string, as in [Stars UNICHAR 11088 & zero-width space (ok)].
- It can also be resolved by using completely different characters, such as "X", as in [Repeated X (ok)].
Conditions that appear produce this behaviour:
- At least one calculation group exists in the model (even if not applied in the report).
- The calculation group must contain a nontrivial calculation item with an expression other than just SELECTEDMEASURE(). In this example, the expression is SELECTEDMEASURE() & ""
- The measure being visualized returns a text value by repeating a single character multiple times.
This can be done with the REPT function or CONCATENATEX/GENERATESERIES.
- More than one "row" of results is returned in the visual.
If we filter Company ID = 2 or 3, the [Stars UNICHAR 11088 (error)] measure returns the correct result.
- Only certain Unicode characters produce this behaviour.
In my testing, characters in the range 11044-11512 mostly cause the bug, with some exceptions (e.g. 11400 & 11480). Characters outside the range 11044-11512 seem fine, e.g. 9733.
- The issue only occurs in Power BI visuals or DAX queries.
If we produce a similar PivotTable in Excel, the measure returns correct results, presumably since the dataset is being queried with MDX. This suggests that this is a DAX engine issue.
Text Measure with Calculation Group Bug v2.pbix
Hi @OwenAuger
You can put your issue to Ideas Forum , if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.
Ideas (powerbi.com)
Best Regards,
Community Support Team _ Ailsa Tao