<?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 Advice on a Pizza model in DAX Commands and Tips</title>
    <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Advice-on-a-Pizza-model/m-p/3301272#M157419</link>
    <description>&lt;P&gt;Hello there. I am trying to improve my modelling technique. I realise my model will change sometimes based on the types of measures I want to create. However right now I'm just trying to do my initial "logical modelling." I'm more than happy to upload the data if needed.&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;STRONG&gt;Question 1:&amp;nbsp;&lt;/STRONG&gt;&lt;/FONT&gt;For the below, for any seasoned data modellers out there with strong DAX capabilities - can you see any floors in my design?&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;STRONG&gt;Question 2:&lt;/STRONG&gt;&lt;/FONT&gt; Is it "right" that I have hidden the Orders table? Or should I simply rather combine the Orders and OrderDetails tables, and just have one table... would it make my DAX simplier?&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;STRONG&gt;Question 3:&lt;/STRONG&gt;&lt;/FONT&gt; I am a bit concerned that I have two dimension tables (Pizzas, PizzaTypes) on top of one "fact" table. Is this okay, is there a special way I would have to handle the DAX here?&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;STRONG&gt;Question 4:&lt;/STRONG&gt;&lt;/FONT&gt; I never know which table is best practice to hide the "id" column. For example, should I hide "pizza_type_id" on the OrderDetails table (but not the PizzTypes table).&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance, Michelle&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 25 Jun 2023 23:26:36 GMT</pubDate>
    <dc:creator>michellepace</dc:creator>
    <dc:date>2023-06-25T23:26:36Z</dc:date>
    <item>
      <title>Advice on a Pizza model</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Advice-on-a-Pizza-model/m-p/3301272#M157419</link>
      <description>&lt;P&gt;Hello there. I am trying to improve my modelling technique. I realise my model will change sometimes based on the types of measures I want to create. However right now I'm just trying to do my initial "logical modelling." I'm more than happy to upload the data if needed.&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;STRONG&gt;Question 1:&amp;nbsp;&lt;/STRONG&gt;&lt;/FONT&gt;For the below, for any seasoned data modellers out there with strong DAX capabilities - can you see any floors in my design?&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;STRONG&gt;Question 2:&lt;/STRONG&gt;&lt;/FONT&gt; Is it "right" that I have hidden the Orders table? Or should I simply rather combine the Orders and OrderDetails tables, and just have one table... would it make my DAX simplier?&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;STRONG&gt;Question 3:&lt;/STRONG&gt;&lt;/FONT&gt; I am a bit concerned that I have two dimension tables (Pizzas, PizzaTypes) on top of one "fact" table. Is this okay, is there a special way I would have to handle the DAX here?&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;STRONG&gt;Question 4:&lt;/STRONG&gt;&lt;/FONT&gt; I never know which table is best practice to hide the "id" column. For example, should I hide "pizza_type_id" on the OrderDetails table (but not the PizzTypes table).&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance, Michelle&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 Jun 2023 23:26:36 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Advice-on-a-Pizza-model/m-p/3301272#M157419</guid>
      <dc:creator>michellepace</dc:creator>
      <dc:date>2023-06-25T23:26:36Z</dc:date>
    </item>
  </channel>
</rss>

