<?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: Multi Tenancy in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/Multi-Tenancy/m-p/2836056#M39205</link>
    <description>&lt;P&gt;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/429085"&gt;@Beniya_Samson&lt;/a&gt;&amp;nbsp;Well, the easiest path to take would be to leverage Row Level Security (RLS). So each customer would be their own role and RLS rules would determine that they only see their own data. Hard to be specific with the information provided. In this scenario, you would have a single data model. And if it is import mode then, yes, it is technically stored as a tabular cube.&lt;/P&gt;</description>
    <pubDate>Wed, 12 Oct 2022 07:51:31 GMT</pubDate>
    <dc:creator>Greg_Deckler</dc:creator>
    <dc:date>2022-10-12T07:51:31Z</dc:date>
    <item>
      <title>Multi Tenancy</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Multi-Tenancy/m-p/2835911#M39203</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;Can Anyone explain how multi tenancy can be enabled in the following Scenario.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have 10 clients with sales transaction in a single table and a single dashboard, each client will have unique id to identify them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;My requirement is:&amp;nbsp; client 1 should be able to access his own data ( other client (2,3...n)&amp;nbsp; data shouldn't be visible /accessible to client1). Will the data be stored in Cubes? How it works?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) How would the refresh and extract will happen?&lt;/P&gt;&lt;P&gt;2) how abt the performance?&lt;/P&gt;&lt;P&gt;3) how it can be implemented ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2022 07:06:09 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Multi-Tenancy/m-p/2835911#M39203</guid>
      <dc:creator>Beniya_Samson</dc:creator>
      <dc:date>2022-10-12T07:06:09Z</dc:date>
    </item>
    <item>
      <title>Re: Multi Tenancy</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Multi-Tenancy/m-p/2836056#M39205</link>
      <description>&lt;P&gt;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/429085"&gt;@Beniya_Samson&lt;/a&gt;&amp;nbsp;Well, the easiest path to take would be to leverage Row Level Security (RLS). So each customer would be their own role and RLS rules would determine that they only see their own data. Hard to be specific with the information provided. In this scenario, you would have a single data model. And if it is import mode then, yes, it is technically stored as a tabular cube.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2022 07:51:31 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Multi-Tenancy/m-p/2836056#M39205</guid>
      <dc:creator>Greg_Deckler</dc:creator>
      <dc:date>2022-10-12T07:51:31Z</dc:date>
    </item>
  </channel>
</rss>

