<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Bug: Base64 Text Measures break down when having Calculation Groups in DAX Commands and Tips</title>
    <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Bug-Base64-Text-Measures-break-down-when-having-Calculation/m-p/3494988#M156377</link>
    <description>&lt;P&gt;Hi all. I have a few &lt;EM&gt;concatenate&lt;/EM&gt;&amp;nbsp;measures to bypass the 32000-character limit in Power BI - They all work fine until I add a calculation group and calculation item - they all break down then. You don't even have to use it - the mere existence of a calculation item is enough to break them. I cannot find much info on the web about this very niche issue. Hopefully, someone has an answer/explanation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Quang&lt;/P&gt;</description>
    <pubDate>Wed, 10 Jan 2024 02:27:02 GMT</pubDate>
    <dc:creator>mmqqq19999</dc:creator>
    <dc:date>2024-01-10T02:27:02Z</dc:date>
    <item>
      <title>Bug: Base64 Text Measures break down when having Calculation Groups</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Bug-Base64-Text-Measures-break-down-when-having-Calculation/m-p/3494988#M156377</link>
      <description>&lt;P&gt;Hi all. I have a few &lt;EM&gt;concatenate&lt;/EM&gt;&amp;nbsp;measures to bypass the 32000-character limit in Power BI - They all work fine until I add a calculation group and calculation item - they all break down then. You don't even have to use it - the mere existence of a calculation item is enough to break them. I cannot find much info on the web about this very niche issue. Hopefully, someone has an answer/explanation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Quang&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2024 02:27:02 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Bug-Base64-Text-Measures-break-down-when-having-Calculation/m-p/3494988#M156377</guid>
      <dc:creator>mmqqq19999</dc:creator>
      <dc:date>2024-01-10T02:27:02Z</dc:date>
    </item>
    <item>
      <title>Re: Bug: Base64 Text Measures break down when having Calculation Groups</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Bug-Base64-Text-Measures-break-down-when-having-Calculation/m-p/5361015#M188448</link>
      <description>&lt;LI-CODE lang="dax"&gt;Calculation Group = IF( ISSELECTEDMEASURE([Base64MeasureName]),       SELECTEDMEASURE(),      You Calculation group code)&lt;/LI-CODE&gt;
&lt;P&gt;Hi &lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="434332" data-lia-user-login="mmqqq19999" class="lia-mention lia-mention-user"&gt;mmqqq19999​&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;You refer that the mere existence of a calculation item breaks the item, when you refer this is to have a slicer on the page were you are using the measures or in any page.&lt;/P&gt;
&lt;P&gt;Can you try to have an exception in the Calculation group something similar to this.&lt;/P&gt;
&lt;P&gt;Be aware that you can use more than one measure inside the ISSELECTEDMEASURE. This code will force the specified measure to be calculated normally.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Aug 2026 09:17:00 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Bug-Base64-Text-Measures-break-down-when-having-Calculation/m-p/5361015#M188448</guid>
      <dc:creator>MFelix</dc:creator>
      <dc:date>2026-08-24T09:17:00Z</dc:date>
    </item>
  </channel>
</rss>

