<?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 Ketan K. on Medium]]></title>
        <description><![CDATA[Stories by Ketan K. on Medium]]></description>
        <link>https://medium.com/@testdev247365?source=rss-a403610cc82------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jg4z2NdzGz_AbStYHnDiEQ.jpeg</url>
            <title>Stories by Ketan K. on Medium</title>
            <link>https://medium.com/@testdev247365?source=rss-a403610cc82------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:36:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@testdev247365/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[Automating Power BI Report Deployment with Dynamic Semantic Model Updates]]></title>
            <link>https://testdev247365.medium.com/automating-power-bi-report-deployment-with-dynamic-semantic-model-updates-463b6daaeda4?source=rss-a403610cc82------2</link>
            <guid isPermaLink="false">https://medium.com/p/463b6daaeda4</guid>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[analysis-services]]></category>
            <category><![CDATA[semantic-model]]></category>
            <category><![CDATA[power-bi]]></category>
            <category><![CDATA[azure-analysis-services]]></category>
            <dc:creator><![CDATA[Ketan K.]]></dc:creator>
            <pubDate>Tue, 18 Mar 2025 15:14:30 GMT</pubDate>
            <atom:updated>2025-03-18T15:14:30.872Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Overview</strong></h3><p>Power BI is a powerful tool for creating interactive reports. Organizations often need to provide <strong>template reports</strong> to Power BI developers, allowing them to quickly create reports with different datasets. The challenge is ensuring that these report templates are updated automatically with new data, while keeping the semantic model compatible with Power BI. This blog post outlines how to automate this process using <strong>Microsoft Analysis Services</strong>, <strong>Power BI Projects</strong>, and the <strong>Fabric API</strong>.</p><h3><strong>Usecase</strong></h3><p>Imagine you are building an <strong>autonomous data flow</strong> system from the backend that needs to integrate with Power BI. This backend system is responsible for generating datasets, preparing data for consumption, and making it available for reporting.</p><p>As part of the automated process, you want to ensure that:</p><ol><li><strong>Power BI Developers</strong> are provided with a <strong>template report</strong> to start building their reports, saving them time and effort in initial setup.</li><li>Each time a new data <em>(tabular form)</em> is provisioned for a user, the <strong>semantic model</strong> for Power BI needs to be updated on the fly to accommodate the new data without disrupting the reporting flow.</li><li>The same <strong>report template</strong> should be reusable, but it must incorporate different tables dynamically, enabling multiple users to work with the same template while accessing different data.</li></ol><p>The core challenge here is ensuring that when new data is available, the underlying semantic model is updated in real-time and then made accessible to Power BI developers. This ensures the correct dataset is loaded into the report template without manual intervention and without causing issues when users attempt to download reports or extract data.</p><h3><strong>The Problem</strong></h3><p>The key issue here lies in <strong>automating the update of the semantic model</strong> for Power BI. The semantic model is critical for defining how datasets and data relationships are structured, and Power BI reports rely on this model to ensure the correct data is displayed.</p><p>When updating the semantic model via <strong>Microsoft.AnalysisServices.Tabular</strong> and provisioning datasets for different users, it is important that:</p><ul><li><strong>All changes to the semantic model</strong> (e.g., adding new tables, columns, or relationships) are fully supported by Power BI.</li><li><strong>Dynamic updates</strong> to the semantic model are seamlessly reflected in the report template without disrupting ongoing report development.</li><li>Users are able to download and interact with reports with <strong>no errors</strong> related to unsupported model changes or data inconsistencies.</li></ul><p>This issue is exacerbated if the semantic model is directly modified via code, as Power BI may not recognize some of the changes, causing <strong>errors</strong> when users attempt to download reports or extract data.</p><h3><strong>The Solution</strong></h3><p>To address these challenges and enable the <strong>autonomous flow</strong> from backend systems while providing <strong>dynamic updates to Power BI’s semantic model</strong>, the solution revolves around:</p><ol><li><strong>Creating a reusable Power BI Report Template</strong> that developers can start with.</li><li><strong>Serializing and updating the semantic model on the fly</strong> each time new data to be provisioned.</li><li><strong>Replacing the semantic model</strong> inside the Power BI project to reflect the new datasets, ensuring consistency and compatibility with Power BI.</li><li><strong>Publishing the updated report</strong> with different datasets using the <strong>Fabric API</strong> to automatically provision user-specific datasets and reports.</li></ol><h4>Steps in detail:</h4><p>Power BI Report Template</p><ul><li>Begin with a <strong>generic Power BI report template</strong> containing placeholders for data.</li><li>This template is designed to work with different datasets, so developers don’t need to recreate the structure for each new dataset.</li></ul><p>Dynamically Update the semantic model</p><ul><li>When new datasets are available, use <strong>Microsoft.AnalysisServices.Tabular</strong> to update the semantic model.</li><li>This involves adding tables, columns, and relationships to the model based on the new dataset.</li><li>Example code to serialize the updated model:</li></ul><pre>using Microsoft.AnalysisServices.Tabular;<br><br>Server server = new Server();<br>server.Connect(connectionString);<br>Model model = server.Databases[&quot;YourDatabase&quot;].Model;<br>model.Save(&quot;UpdatedModel.bim&quot;);</pre><p>Replace the .bim File</p><ul><li>Replace the old .bim file in the <strong>Power BI Project</strong> with the new one. The .bim file defines the schema for the report and ensures that Power BI uses the updated semantic model.</li></ul><p>Publish via the Fabric API</p><ul><li>Use the <strong>Fabric API</strong> to automatically upload the updated Power BI report with the new semantic model to the workspace.</li><li>This ensures the report is published with the correct dataset for each user.</li></ul><pre>var fabricClient = new FabricClient(apiKey);<br>fabricClient.UploadPowerBIProject(&quot;path/to/UpdatedPowerBIProject.pbix&quot;, workspaceId);</pre><h3>Conclusion</h3><p>By automating the update of the semantic model and publishing reports via the <strong>Fabric API</strong>, organizations can streamline the process of providing dynamic, up-to-date Power BI reports. This solution ensures that report templates are always aligned with the latest data, enabling developers to focus on building insights rather than managing dataset configurations. The automation helps improve consistency, scalability, and the overall user experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=463b6daaeda4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“It works for me”, now works for everyone !!]]></title>
            <link>https://testdev247365.medium.com/it-works-for-me-now-works-for-everyone-cdd049d6bc63?source=rss-a403610cc82------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdd049d6bc63</guid>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[remote-containers]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[remote-development]]></category>
            <dc:creator><![CDATA[Ketan K.]]></dc:creator>
            <pubDate>Sat, 06 Mar 2021 19:38:15 GMT</pubDate>
            <atom:updated>2022-12-05T15:12:26.357Z</atom:updated>
            <content:encoded><![CDATA[<h3>“It works for me”, now works for everyone !!</h3><h3>Remote-Containers for development with VS Code and Docker</h3><blockquote><em>Development inside a </em><strong><em>devContainer</em></strong><em> with VS Code makes the project setup uniform for everyone in the team with same project dependencies.</em></blockquote><p>During the development phase, for big projects which depends on multiple sub projects with different technology stack, face the problems like different versions of framework in individual machines, running two projects with different configuration of same framework etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EwJAr5nTXGiRNPfXzRmpRg.png" /><figcaption>One project with multiple sub projects on different stack/versions</figcaption></figure><p><em>Here is the solution:</em></p><p>The <a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers"><strong>Remote — Containers</strong></a> extension, lets you run Visual Studio Code inside a Docker container and it provides you a complete isolated environment on top of your OS.</p><p>It helps to convert the repository/folder into a remote container by adding required meta files under <strong>.devcontainer</strong> folder. The <strong>devcontainer.json</strong> file contains all the configurations related to creation/access of development container like dockerfile name, args to be passed to the container, setting vs code integrated terminal (for example: bash or zsh), vs code extensions, postcreatecommand etc.</p><p>While adding the devcontainer configuration, you can choose among the dev container definitions which are displayed based on the project which is open in VS Code or if you have your customized Dockerfile, then you can provide that too.</p><p>After adding the configuration w.r.t project tech stack, you can reopen your folder to develop in a container. It will start setting up the container based on devcontainer.json configuration and respective docker file. Fetching the base image for the first time takes sometime (depending on network speed), later it’s been cached.</p><p>Once the container is up and running (after executing postCreateCommand, defined in devcontainer.json), you get an isolated container with all the frameworks and required dependencies setup.</p><p>You are ready to start development !!</p><p>For setting up dev container into a project from scratch, refer: <a href="https://code.visualstudio.com/docs/remote/containers#_getting-started">https://code.visualstudio.com/docs/remote/containers#_getting-started</a></p><p>Github Sample: <a href="https://github.com/kharedev247/DevContainers-TestApp">https://github.com/kharedev247/DevContainers-TestApp</a></p><p>Thanks for reading<em> Remote-Containers with VS Code and Docker</em>. Reach me with tips and feedback on LinkedIn: <a href="https://www.linkedin.com/in/ketankhare/">https://www.linkedin.com/in/ketandev/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdd049d6bc63" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>