<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Keerthi Kurra on Medium]]></title>
        <description><![CDATA[Stories by Keerthi Kurra on Medium]]></description>
        <link>https://medium.com/@keerthi.kurra20?source=rss-d04c50509fa9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*eYWgOQSSP5l4KT3g</url>
            <title>Stories by Keerthi Kurra on Medium</title>
            <link>https://medium.com/@keerthi.kurra20?source=rss-d04c50509fa9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:27:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@keerthi.kurra20/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Best practices for Application development in Power BI]]></title>
            <link>https://medium.com/@keerthi.kurra20/best-practices-for-application-development-in-power-bi-18cbe22ed710?source=rss-d04c50509fa9------2</link>
            <guid isPermaLink="false">https://medium.com/p/18cbe22ed710</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[dashboard]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[power-bi]]></category>
            <dc:creator><![CDATA[Keerthi Kurra]]></dc:creator>
            <pubDate>Sat, 22 Apr 2023 13:05:29 GMT</pubDate>
            <atom:updated>2023-04-22T13:05:29.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/133/1*BT8Dunq9QcvMwgALXLYDYw@2x.jpeg" /></figure><blockquote>There are numerous Power BI-based dashboards that are used by thousands of enterprise users every day in order to drive operations as well as marketing. This article intends to introduce you to the best practices of Power BI.</blockquote><blockquote><strong>1) Data Modeling</strong></blockquote><p>Decide the data connectivity mode correctly</p><p>(Guidance) -Import Mode, Direct query, Live connection</p><p>• Reduce dataset size by including only required column from SELECT statement in case of RDBMS. When having source as file do not import unnecessary columns.</p><p>Two of the main ways to reduce the amount of data stored in a dataset include:</p><ul><li>1. Removing columns from source tables in the Query</li><li>Editor.</li><li>2. Filtering rows from the source tables down to just the</li><li>subset of data which is required.</li><li>• Retrieve Source data from a database View in case of</li><li>RDBMS.</li></ul><p>To maximize performance, aim to minimize both the amount of data displayed as well as the number of visuals displayed on a page.</p><p>Consider “Assume referential Integrity” property to improve query efficiency in case of Direct query mode.</p><p>Use business user friendly Name for tables to maintain Semantic layer.</p><p>Validate all the table relationships are accurate as per our need.</p><p>Prefer Star Schema in reporting model over Snowflake schema to avoid unnecessary joins to increase performance of your model.</p><p>Validate Bi-directional relationships and Inactive relationships purposefully.</p><p>Turn off auto date time from options and settings to avoid unnecessary creation of temporary date time tables.</p><p>Disable load for intermediary queries such as when two queries are then merged together into one any intermediary queries should be disabled from being loaded to the data model.</p><p>Consider Reusing an Existing Datasets for multiple reports.</p><p>Disable below two settings as we do not want to loose</p><ul><li>existing relationship without our knowledge.</li><li>Update relationships when refreshing queries</li><li>Autodetect new relationships after data is loaded</li><li>Create parameterize data Source connections or other</li><li>Changing Data as it is useful to minimize hard-coding and</li><li>reduce maintenance when changes need to occur.</li></ul><p>Set Encryption for Data Source Connections as Connections should be encrypted whenever possible as a standard security measure.</p><p>Use Consistent source file locations in case of data source as file.</p><p>Include description for Query to know its purpose if it is doing something unusual.</p><p>Use proper naming of query Steps for better understanding of the steps.</p><p>Create Unique field Names across the entire dataset.</p><p>Hide fields not utilized for reporting. E.g. IDs and surrogate keys are needed for relationships, but are not useful for reporting.</p><p>Consider using business user Friendly names for fields.</p><p>Set Formatting for all Numeric and Date Fields.</p><p>Create useful Calculated Columns and Calculated Measures</p><p>Keep all your measures in one place / table as best practice.</p><p>Set the data category as required. Address-related columns,such as city/state/zip and so forth, need to bespecified in the data model to ensure geocoding can occur properly.</p><p>Create hierarchies for better usability.</p><p>Create Date table with specific fields as needed as it is best practice.</p><p><strong><em>2) Visualization</em></strong></p><p>Consider Using a common Power BI Template and theme while creating reports.</p><p>Limit the visuals on dashboards and reports. As placing multiple visuals on single page hampers it’s performance.</p><p>Consider using slicers and filters in your reports to allow the user to select just the data that is needed to be displayed at any one time.</p><p>Techniques such as bookmarks and drillthrough pages can be used to reduce the amount of data displayed on a page.</p><p>Have a specific purpose for each page, and for each chart on each page.</p><p>Include clear interactions and instructions for report consumers.</p><p>Choose a color theme that has a high degree of contrast between backgrounds and text which make reports easier to read.</p><p>Use Microsoft AppSource certified custom visuals in our reports.</p><p>Test each custom visual on a report for ensuring fast report load time.</p><p>Create synonyms to improve Q&amp;A experience. As</p><p>thoughtful creation of synonyms improves the user experience significantly so that users do not always have to input field names exactly.</p><p>Use a consistent unchanging PBIX File Name with business relevance.</p><p>Set Up Row Level Security (Standard or Dynamic as per situation). As it useful to specify which rows of data certain users are permitted to view.</p><p><strong><em>3) DAX and Report Documentation</em></strong></p><p>Use proper naming convention when referencing measures and columns (e.g. Table name as a prefix)</p><p>Use Error messaging in DAX. Error() function provides a</p><ul><li>description if a calculation result cannot be rendered.</li></ul><p>Consider Using the Divide() Function in place of “/”. As we</p><ul><li>don’t have to worry about nulls or coding around divide-by-zero errors.</li></ul><p>Use variables as a common practice in DAX expressions.</p><p>Consider solution documentation. Such as using the first or last report page as a place to include helpful tips,definitions, or an introduction to the solution.</p><p>Descriptions for fields as it is helpful for users to understand</p><ul><li>the contents of a column or measure, when and how to use it.</li><li>Mention Comments in DAX Calculations M script</li></ul><p>There are few more best practices too which help us creating the best version of dashboards!! Do check out and let me know your thoughts through comments!!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18cbe22ed710" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Power BI -#2 Report Bursting to Email, SharePoint, one drive.]]></title>
            <link>https://medium.com/@keerthi.kurra20/power-bi-2-report-bursting-to-email-sharepoint-one-drive-3e7fb9be661b?source=rss-d04c50509fa9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e7fb9be661b</guid>
            <dc:creator><![CDATA[Keerthi Kurra]]></dc:creator>
            <pubDate>Sat, 15 Apr 2023 05:36:45 GMT</pubDate>
            <atom:updated>2023-04-15T05:36:45.144Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*f-6cJzxfzQEsZ1G3GtWPtQ.jpeg" /><figcaption>Report Bursting</figcaption></figure><p>✨ <strong>Use case</strong>: History tracking and ease of accessing the reports has become a must and should need for most of the projects. Data analysis of the paginated report in their pixel perfect format enables thorough understanding of the data and also gives an ease of evaluation.<br>✨ <strong>Tools in the picture</strong>: Power BI desktop, Report builder, Power Automate.<br>✨ <strong>Overview</strong>: “Report Bursting &quot;is the ability to render the same report multiple times with different values based on filters or parameters. Each uniquely rendered report is delivered in a uniquely specified format and delivered to a uniquely identified recipient.</p><p>Report bursting in our project sense has come into picture for security reasons. We didn’t want the traditional method of email subscriptions which send in the link to the report or with an attached image to the user which could just pass on and hinder the security aligned. However we also wanted to track the history of report run and have a source of truth stored at a SharePoint /one drive. While the limitations exist and their own pro’s outgrow, we have found a way to render the report using parameters and share the report by creating a flow using Power automate(a pinch of automation always dominates manual efforts!! :D)<br>✨ <strong>Process of Implementation:</strong><br><strong>Step 1</strong>: Create a power bi desktop report or a paginated report and deploy into power bi service.<br><strong>Step 2</strong>: once the report is successfully deployed, ensure to place it in appropriate workspaces.<br><strong>Step 3</strong>: Login to Microsoft Power Automate → Click on create →depending on the need and requirement choose a type of flow (we need a scheduled flow for our project so selected it)<br><strong>Step 4</strong>: Set a recurrence schedule for the flow to run and the report to be exported in the defined format<br><strong>Step 5</strong>: (Note we covered a couple of scenarios here)<br>🚀 → Created a flow element to export a paginated report to a file(in any format)<br>🚀 → Created a flow element to export a power Bi report to a SharePoint /OneDrive/email in specified set of formats(PDF/PPTX)<br>🚀 → Created a flow element to run the query against the dataset for sourcing the csv file thereby the SharePoint excel<br>🚀 →Created a flow element to loop over the data in an excel file for generating the report to unique set of users based on parameters.</p><p><strong>Step 6</strong>: once the mail flow element is defined we add on steps necessary to capture the data from step 5 and add our set of transformations whether it is for an addition of utc stamp for historical purposes, distinguishing nomenclature for the files etc.<br>Once the flow is setup, we can run the flow manually to test it or leave it for the set recurred time for it to run. We can monitor the report rendered and delivered using the flow run page which also captures the runs for the flow.</p><p>This is an interesting learning! Do share your thoughts/suggestions and experiments with power automate if any!</p><p><a href="https://www.linkedin.com/feed/hashtag/?keywords=microsoftpowerautomate&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7052873704199884800">#microsoftpowerautomate</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=reportbursting&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7052873704199884800">#reportbursting</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=powerbi&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7052873704199884800">#powerbi</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e7fb9be661b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Power BI- #1 Dynamic Data Source(connection string)& Gateway Change using Parameters in Power…]]></title>
            <link>https://medium.com/@keerthi.kurra20/power-bi-1-dynamic-data-source-connection-string-gateway-change-using-parameters-in-power-5d0db0487e69?source=rss-d04c50509fa9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d0db0487e69</guid>
            <category><![CDATA[power-bi-report-builder]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[report]]></category>
            <category><![CDATA[denodo]]></category>
            <category><![CDATA[power-bi]]></category>
            <dc:creator><![CDATA[Keerthi Kurra]]></dc:creator>
            <pubDate>Sat, 15 Apr 2023 05:30:44 GMT</pubDate>
            <atom:updated>2023-04-15T05:30:44.191Z</atom:updated>
            <content:encoded><![CDATA[<h3>Power BI- #1 Dynamic Data Source(connection string)&amp; Gateway Change using Parameters in Power BI-For Denodo</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/1*jREcdh691gLxOyz8IJP-AA.jpeg" /><figcaption>Dynamic Parameter changes</figcaption></figure><p><strong>USE Case</strong>: Data change with respect to its source is a common use case that we encounter in our project activities. What if we could dynamically move across connections and map their respective gateways in power bi service depending on the parameter connection’s. This scenario is achievable using the functionality of parameters and their given possibility to enter a multiple set of values which could be connection strings pertaining to a server with their port information.</p><p><strong>Simple steps for the configuration:</strong></p><p><strong>Step 1</strong>: Create a new parameter in the power query editor by providing the name, Description, Required field details and the values of the parameters in 3 was -(Any value, List of values and query).<br><strong>Step 2</strong>: Publish the report to power bi service and once the report is published, the connection string can be configured with any of the parameter values provided in the list of values<br><strong>Step 3</strong>: To change the connection, we need to shift in the parameter values. then click on apply and refresh the page this should automatically shift the respective gateway created.</p><p>Note: Here the connection string used was for Denodo. in the form of &lt;server:&gt;;&lt;database&gt;;&lt;port&gt;, license on service is premium per user and this configuration is setup to move the connection across different environments(UAT,UNT,PROD etc..).</p><p><strong>Requirement</strong>: This is the same connection model we are trying to achieve in the Power BI report builder without the DSN connection so that the gateway is appropriately mapped. Do put in your comments, start in discussion to add on your thoughts on the same.</p><p><a href="https://www.linkedin.com/feed/hashtag/?keywords=parameters&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7050369922920529920">#parameters</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=powerbidesktop&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7050369922920529920">#powerbidesktop</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=gateway&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7050369922920529920">#gateway</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=denodo&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7050369922920529920">#denodo</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=dsn&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7050369922920529920">#DSN</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=configuration&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7050369922920529920">#configuration</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d0db0487e69" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>