<?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 Re: CONCAT in a measure which should behave like a column in DAX Commands and Tips</title>
    <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/CONCAT-in-a-measure-which-should-behave-like-a-column/m-p/4029542#M159267</link>
    <description>&lt;P&gt;Thank you for your reply, &lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="501067" data-lia-user-login="Sahir_Maharaj" class="lia-mention lia-mention-user"&gt;Sahir_Maharaj&lt;/a&gt;&amp;nbsp;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately creating a new table with SUMMARIZE saves the new table in memory again, so this does not solve my primary problem of having a semantic model that is too big (in GB) due to the high cardinality of the transactionID column.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jul 2024 11:45:12 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-07-08T11:45:12Z</dc:date>
    <item>
      <title>CONCAT in a measure which should behave like a column</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/CONCAT-in-a-measure-which-should-behave-like-a-column/m-p/4027160#M159052</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a transactionID that I have split up in two parts for memory reasons (very high cardinality). See here:&amp;nbsp;&lt;A href="https://www.sqlbi.com/articles/optimizing-high-cardinality-columns-in-vertipaq/" target="_blank" rel="noopener"&gt;Optimizing High Cardinality Columns in VertiPaq - SQLBI&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now in Desktop I am trying to bring these two parts together again in a measure (not in a calculated measure as that would use memory again). According to the example this is possible with (although I have used SELECTEDVALUE instead of VALUES):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;VALUES( Fact[TransactionHighID] ) * 10000 + VALUES( Fact[TransactionLowID] )&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, it does not behave as I would like it to be. What I want if I create a table visual is that I get a row for every unique value of the TransactionID.&lt;/P&gt;&lt;P&gt;E.g.:&lt;/P&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Color&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;&lt;STRONG&gt;TransactionID&lt;/STRONG&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Blue&lt;/TD&gt;&lt;TD&gt;13345678&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Blue&lt;/TD&gt;&lt;TD&gt;12845679&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Yellow&lt;/TD&gt;&lt;TD&gt;16345666&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Yellow&lt;/TD&gt;&lt;TD&gt;17895699&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But what I get is an empty table visual.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2024 14:06:04 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/CONCAT-in-a-measure-which-should-behave-like-a-column/m-p/4027160#M159052</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-07-05T14:06:04Z</dc:date>
    </item>
    <item>
      <title>Re: CONCAT in a measure which should behave like a column</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/CONCAT-in-a-measure-which-should-behave-like-a-column/m-p/4028706#M159188</link>
      <description>&lt;P&gt;Hello&amp;nbsp;Anonymous&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you please try&amp;nbsp;creating a new table in Power BI to help achieve this:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;UniqueTransactionTable = 
    SUMMARIZE(
        'Fact',
        'Fact'[Color],
        'Fact'[TransactionHighID],
        'Fact'[TransactionLowID],
        "TransactionID", 'Fact'[TransactionHighID] * 10000 + 'Fact'[TransactionLowID]
    )
&lt;/LI-CODE&gt;
&lt;P&gt;Let me know if you might require my further input.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jul 2024 13:28:15 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/CONCAT-in-a-measure-which-should-behave-like-a-column/m-p/4028706#M159188</guid>
      <dc:creator>Sahir_Maharaj</dc:creator>
      <dc:date>2024-07-07T13:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: CONCAT in a measure which should behave like a column</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/CONCAT-in-a-measure-which-should-behave-like-a-column/m-p/4029542#M159267</link>
      <description>&lt;P&gt;Thank you for your reply, &lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="501067" data-lia-user-login="Sahir_Maharaj" class="lia-mention lia-mention-user"&gt;Sahir_Maharaj&lt;/a&gt;&amp;nbsp;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately creating a new table with SUMMARIZE saves the new table in memory again, so this does not solve my primary problem of having a semantic model that is too big (in GB) due to the high cardinality of the transactionID column.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 11:45:12 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/CONCAT-in-a-measure-which-should-behave-like-a-column/m-p/4029542#M159267</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-07-08T11:45:12Z</dc:date>
    </item>
  </channel>
</rss>

