<?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: Data Modelling Issue (Many to Many between Fact and Dimension) in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3684219#M49422</link>
    <description>&lt;P&gt;Hi , Thank you all for responding. A bridge table did not resolve it. I went with a M-M bi-directional join and enabled the 'show items with no data' so this gave me the expected results of a left outer join by bringing in only the program codes of the Purchase order used from fact.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Feb 2024 23:25:08 GMT</pubDate>
    <dc:creator>RRaj_293</dc:creator>
    <dc:date>2024-02-06T23:25:08Z</dc:date>
    <item>
      <title>Data Modelling Issue (Many to Many between Fact and Dimension)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3664315#M49190</link>
      <description>&lt;P&gt;Hello ,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help with the below data modelling question-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a fact table called purchase Order and few other dimensions connected in star schema . Now I have brought in a connection to smartsheet and the columns in both the fact and smart sheet table is as shown-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Purchase Order Fact Table&amp;nbsp;&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Purchase Order&lt;/TD&gt;&lt;TD&gt;Line Number&lt;/TD&gt;&lt;TD&gt;Ordered Units&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;ABC1&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;TD&gt;4&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;ABC1&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;ABC1&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;PQR2&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;TD&gt;13&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;PQR2&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;TD&gt;24&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;PQR2&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;PQR2&lt;/TD&gt;&lt;TD&gt;4&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;XYZ3&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;XYZ3&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;TD&gt;8&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;XYZ3&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Smart Sheet Table-&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Program Code&lt;/TD&gt;&lt;TD&gt;Program Name&lt;/TD&gt;&lt;TD&gt;Purchase Order&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;123&lt;/TD&gt;&lt;TD&gt;united pgm&lt;/TD&gt;&lt;TD&gt;ABC1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;345&lt;/TD&gt;&lt;TD&gt;Exclusive pgm&lt;/TD&gt;&lt;TD&gt;ABC1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;678&lt;/TD&gt;&lt;TD&gt;Rep Pgm&lt;/TD&gt;&lt;TD&gt;PQR&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;123&lt;/TD&gt;&lt;TD&gt;united pgm&lt;/TD&gt;&lt;TD&gt;XYZ3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;678&lt;/TD&gt;&lt;TD&gt;Rep Pgm&lt;/TD&gt;&lt;TD&gt;XYZ3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Purchase Order is the only common field(joining field) between both the fact and smart sheet table.&lt;/P&gt;&lt;P&gt;- One purchase order in Smart sheet table could belong to more than 1 program and hence can have more than one&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;program&amp;nbsp; code. This results in a M-M relationship as shown in table above(Multiple records of purchase order).&lt;/P&gt;&lt;P&gt;- In the Power BI report , Purchase order Number is used for display from Fact table and only 'Program Code' and 'Program Name' is used from Smartsheet table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem - I tried single and bi-directional filter for the M-M relationship between these two tables they are not yielding right results. Even if I create a bridging table it would have one purchase order occuring twice because of the program codes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please advise how fix this data model issue.&lt;/P&gt;</description>
      <pubDate>Sat, 27 Jan 2024 17:25:05 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3664315#M49190</guid>
      <dc:creator>RRaj_293</dc:creator>
      <dc:date>2024-01-27T17:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: Data Modelling Issue (Many to Many between Fact and Dimension)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3666280#M49202</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;try creating a bridge/factless fact table it will solve your many to many relationship problem.&lt;BR /&gt;if your don't know about&amp;nbsp;bridge/factless fact table you can search on google that how to build one and what are the use cases of it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this is helpfull&lt;/P&gt;&lt;P&gt;thank you&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2024 13:46:45 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3666280#M49202</guid>
      <dc:creator>Burhan_Jiru</dc:creator>
      <dc:date>2024-01-29T13:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: Data Modelling Issue (Many to Many between Fact and Dimension)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3666970#M49210</link>
      <description>&lt;P&gt;That is not a Purchase Order Fact Table. It is a PO Line Item fact table.&amp;nbsp; Add a PO dimension table in between.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2024 21:57:52 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3666970#M49210</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2024-01-29T21:57:52Z</dc:date>
    </item>
    <item>
      <title>Re: Data Modelling Issue (Many to Many between Fact and Dimension)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3684219#M49422</link>
      <description>&lt;P&gt;Hi , Thank you all for responding. A bridge table did not resolve it. I went with a M-M bi-directional join and enabled the 'show items with no data' so this gave me the expected results of a left outer join by bringing in only the program codes of the Purchase order used from fact.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Feb 2024 23:25:08 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Data-Modelling-Issue-Many-to-Many-between-Fact-and-Dimension/m-p/3684219#M49422</guid>
      <dc:creator>RRaj_293</dc:creator>
      <dc:date>2024-02-06T23:25:08Z</dc:date>
    </item>
  </channel>
</rss>

