<?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 Facts and Dims in Dataflow</title>
    <link>https://community.fabric.microsoft.com/t5/Dataflow/Facts-and-Dims/m-p/4313158#M4688</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How does everyone approach modeling in Dataflows Gen2? For our client it seems easier to do it with a dataflow because they are not on a sufficient SQL or notebook level.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would you create a dataflow for every fact/dim? It makes sense for me to keep it seperate. But i'm also thinking - if multiple facts/dims use the same source tables that we might combine them into one dataflow&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 04 Dec 2024 09:15:14 GMT</pubDate>
    <dc:creator>dpjatochh</dc:creator>
    <dc:date>2024-12-04T09:15:14Z</dc:date>
    <item>
      <title>Facts and Dims</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Facts-and-Dims/m-p/4313158#M4688</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How does everyone approach modeling in Dataflows Gen2? For our client it seems easier to do it with a dataflow because they are not on a sufficient SQL or notebook level.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would you create a dataflow for every fact/dim? It makes sense for me to keep it seperate. But i'm also thinking - if multiple facts/dims use the same source tables that we might combine them into one dataflow&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2024 09:15:14 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Facts-and-Dims/m-p/4313158#M4688</guid>
      <dc:creator>dpjatochh</dc:creator>
      <dc:date>2024-12-04T09:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: Facts and Dims</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Facts-and-Dims/m-p/4314121#M4692</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="833434" data-lia-user-login="dpjatochh" class="lia-mention lia-mention-user"&gt;dpjatochh&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;I would suggest here to go by Dataflow best practices.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;You can have first dataflow to bring in your raw data. (Staging Dataflow)&lt;/LI&gt;
&lt;LI&gt;You can have second dataflow to do all the transformations like creating DIM and FACT tables. (Transformation Dataflow)&lt;/LI&gt;
&lt;LI&gt;Finally you can have a dataflow having all your final transformed tables (DIMS and FACTS); which you can use further to create your semantic model. (Output Dataflow)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Staging DF --&amp;gt; Transformation DF --&amp;gt; Output DF&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can read about dataflow best practices here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/power-query/dataflows/best-practices-developing-complex-dataflows" target="_blank"&gt;https://learn.microsoft.com/en-us/power-query/dataflows/best-practices-developing-complex-dataflows&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2024 22:57:58 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Facts-and-Dims/m-p/4314121#M4692</guid>
      <dc:creator>Pragati11</dc:creator>
      <dc:date>2024-12-04T22:57:58Z</dc:date>
    </item>
  </channel>
</rss>

