<?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 Filter a report using query string parameters in the URL in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/Filter-a-report-using-query-string-parameters-in-the-URL/m-p/4201411#M56663</link>
    <description>&lt;P&gt;"I’m working on a Power BI project where I need to build a report that serves multiple clients. I’m considering using a single dataset and applying filters via a query string (e.g., ClientID=123) combined with Row-Level Security (RLS) to restrict data access. For those who have worked with this approach, how does it scale in terms of performance and security when dealing with large datasets? Any potential drawbacks to watch out for?"&lt;/P&gt;</description>
    <pubDate>Mon, 30 Sep 2024 14:47:17 GMT</pubDate>
    <dc:creator>VenkatC</dc:creator>
    <dc:date>2024-09-30T14:47:17Z</dc:date>
    <item>
      <title>Filter a report using query string parameters in the URL</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Filter-a-report-using-query-string-parameters-in-the-URL/m-p/4201411#M56663</link>
      <description>&lt;P&gt;"I’m working on a Power BI project where I need to build a report that serves multiple clients. I’m considering using a single dataset and applying filters via a query string (e.g., ClientID=123) combined with Row-Level Security (RLS) to restrict data access. For those who have worked with this approach, how does it scale in terms of performance and security when dealing with large datasets? Any potential drawbacks to watch out for?"&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 14:47:17 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Filter-a-report-using-query-string-parameters-in-the-URL/m-p/4201411#M56663</guid>
      <dc:creator>VenkatC</dc:creator>
      <dc:date>2024-09-30T14:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Filter a report using query string parameters in the URL</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Filter-a-report-using-query-string-parameters-in-the-URL/m-p/4202118#M56691</link>
      <description>&lt;P&gt;This is a doomed approach.&amp;nbsp; URL filters are the opposite of RLS.&amp;nbsp; Use separate reports.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 17:28:57 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Filter-a-report-using-query-string-parameters-in-the-URL/m-p/4202118#M56691</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2024-09-30T17:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: Filter a report using query string parameters in the URL</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Filter-a-report-using-query-string-parameters-in-the-URL/m-p/4202150#M56693</link>
      <description>&lt;DIV class=""&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;I have a database containing client details, and I want to create a report for each client. Even though the reports will be similar, I aim to implement a single report that can be used for multiple clients. I'm exploring two methods: 1) filtering a report using query string parameters in the URL, and 2) dynamically binding datasets to a paginated report.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 30 Sep 2024 17:46:29 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Filter-a-report-using-query-string-parameters-in-the-URL/m-p/4202150#M56693</guid>
      <dc:creator>VenkatC</dc:creator>
      <dc:date>2024-09-30T17:46:29Z</dc:date>
    </item>
  </channel>
</rss>

