<?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: Dynamic RLS in Power BI in DAX Commands and Tips</title>
    <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Dynamic-RLS-in-Power-BI/m-p/4421862#M175556</link>
    <description>&lt;P&gt;Create a new table like&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;RLS Table =
SUMMARIZE (
    'Default Account Team',
    'Default Account Team'[Email],
    'Default Account Team'[User ID]
)
&lt;/LI-CODE&gt;
&lt;P&gt;And link this to the default account team. That should be one-to-many.&lt;/P&gt;
&lt;P&gt;Many-to-many relationships are OK for the other tables, but make sure that they are single-direction, so that default account team filters project share and project share filters projects.&lt;/P&gt;
&lt;P&gt;Create a security role and add a filter so that 'RLS Table'[Email] = USERPRINCIPLENAME().&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2025 11:49:38 GMT</pubDate>
    <dc:creator>johnt75</dc:creator>
    <dc:date>2025-02-21T11:49:38Z</dc:date>
    <item>
      <title>Dynamic RLS in Power BI</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Dynamic-RLS-in-Power-BI/m-p/4421779#M175554</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am facing one challenge while implementing the Dynamic RLS in my project, please help with the scenario and data modelling.&lt;/P&gt;&lt;P&gt;Scenario with the below 3 tables involved,&lt;BR /&gt;1. Projects - This is the main table and acts as fact table having the ID coulmns, accounts info and base measures. Key columns are(ID)&lt;/P&gt;&lt;P&gt;2. Projects Share - This table having UserID &amp;amp; ParentID info, it is having relationship with ID column to the Projects table and also UserID can join the Account Default table which is the below 3 table.&amp;nbsp;Key columns are (ParentID) &amp;amp; (UserID)&lt;/P&gt;&lt;P&gt;3. Default Account Team - This table having the User info including User name, email etc also what are Specific accounts added to the user.&amp;nbsp;Key columns are(UserID)&lt;BR /&gt;Note: when I make the relationship between Projects Share &amp;amp; Default Account Table is having Many to Many relationship.&lt;BR /&gt;&lt;BR /&gt;please help me to implement the Dynamic RLS in this datamodelling scenario.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Bala&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2025 10:48:57 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Dynamic-RLS-in-Power-BI/m-p/4421779#M175554</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-02-21T10:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic RLS in Power BI</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Dynamic-RLS-in-Power-BI/m-p/4421862#M175556</link>
      <description>&lt;P&gt;Create a new table like&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;RLS Table =
SUMMARIZE (
    'Default Account Team',
    'Default Account Team'[Email],
    'Default Account Team'[User ID]
)
&lt;/LI-CODE&gt;
&lt;P&gt;And link this to the default account team. That should be one-to-many.&lt;/P&gt;
&lt;P&gt;Many-to-many relationships are OK for the other tables, but make sure that they are single-direction, so that default account team filters project share and project share filters projects.&lt;/P&gt;
&lt;P&gt;Create a security role and add a filter so that 'RLS Table'[Email] = USERPRINCIPLENAME().&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2025 11:49:38 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Dynamic-RLS-in-Power-BI/m-p/4421862#M175556</guid>
      <dc:creator>johnt75</dc:creator>
      <dc:date>2025-02-21T11:49:38Z</dc:date>
    </item>
  </channel>
</rss>

