Tag: powerbi

  • Use SVG, HTML & CSS to enhance PowerBI reports

    Use SVG, HTML & CSS to enhance PowerBI reports

    HTML, CSS and SVGs are some of the things I know relatively well, Ive always messed around making games, animating or building apps out of various methods. In this case I wanted to understand how I can use SVG, HTML & CSS to enhance PowerBI reports.

    PowerBI whilst it has a lot of options in terms of its custom visuals, that same flexibility isnt always there. Difference is now you can use SVGs & HTML in tables, cards and all sorts just the same as if you were coding in a webpage. A lot of amazing content creators have already covered a lot of use cases for using HTML & SVG in things like tables. I wanted to do something a bit different, taking a look at those more traditional HTML methods I know for adding things like animation.

    What I have built out as part of this blog post can then be used as a base for building out pretty much anything when it comes to using SVGs and HTML. Throw in animation, changing colors anything you can think of.

    I love that these things also feed into my role as a Product Manager. I can dabble, play and find new ways to make UI / UX more exciting and engaging for my customers.

    Setting up the SVG / HTML Measure

    Firstly, for these initial cases I am just using the built in PowerBI visuals. To make this work we have to load the SVG / HTML in via a measure.

    I have created two base measures to cover common scenarios, depending on your needs (note we can not use JavaScript in either with PowerBI)

    • Using <foreignObject> to embed extended HTML and CSS inside SVG
    • Using pure SVG native elements

    FeatureSVG Native<foreignObject> (Extended HTML inside SVG)
    CSS SupportLimited to SVG and subset of CSSFull CSS including advanced layout, pseudo-elements
    Browser & tool supportVery broad, stableGood in modern browsers, less consistent in tools like Power BI
    Use casesSimple vector graphics, text, shapesComplex layouts, rich text formatting inside SVG
    PerformanceLightweight, fastSlightly heavier, potentially slower
    InteractivitySVG events and styling onlyCan use HTML events and richer interaction

    <foreignObject> Base

    HTMLBASE_FO = 
    
    -- Get the percentage value from a slicer or parameter table (assumes 0 to 1 scale)
    VAR pct = Parameter1[Parameter Value]
    
    -- Format the percentage as a whole number string with a "%" sign (e.g., "85%")
    VAR pctText = FORMAT(pct * 100, "0") & "%"
    
    -- Define the size of the SVG image
    VAR sizeWidth = 320
    VAR sizeHeight = 180
    
    -- Define dynamic colours
    VAR baseColor = "#292929"
    VAR textColor = "#f5f5f5"
    VAR subtitleColor = "#bbb"
    
    -- Build the HTML block for the foreignObject
    VAR svghtml = "
    <foreignObject x='0' y='0' width='" & sizeWidth & "' height='" & sizeHeight & "'>
      <div xmlns='http://www.w3.org/1999/xhtml'>
        <style>
          .card {
            width: 100%;
            height: 100%;
            background-color: " & baseColor & ";
            border-radius: 20px;
            padding: 24px;
            box-sizing: border-box;
            font-family: Segoe UI, sans-serif;
            display: flex;
            flex-direction: column;
            justify-content: center;
          }
          .title {
            font-size: 22px;
            font-weight: 600;
            color: " & textColor & ";
          }
          .value {
            font-size: 64px;
            font-weight: 900;
            color: " & textColor & ";
            margin-top: 4px;
          }
          .subtitle {
            font-size: 14px;
            color: " & subtitleColor & ";
            margin-top: auto;
          }
        </style>
        <div class='card'>
          <div class='title'>Title</div>
          <div class='value'>" & pctText & "</div>
          <div class='subtitle'>SubTitle</div>
        </div>
      </div>
    </foreignObject>
    "
    
    -- Wrap the foreignObject in an SVG
    VAR svg = "<svg xmlns='http://www.w3.org/2000/svg' width='" & sizeWidth & "' height='" & sizeHeight & "'>" & svghtml & "</svg>"
    
    -- Return the inline image
    RETURN "data:image/svg+xml;utf8," & svg

    SVG Native Base

    HTMLBASE_SVG = 
    VAR pct = Parameter1[Parameter Value]
    VAR pctText = FORMAT(pct * 100, "0") & "%"
    VAR sizeWidth = 320
    VAR sizeHeight = 180
    
    VAR baseColor = "#292929"
    VAR textColor = "#f5f5f5"
    VAR subtitleColor = "#bbb"
    
    VAR fillColor =
        SWITCH(
            TRUE(),
            pct < 0.2, "#E59EFB",
            pct > 0.8, "#F8FAB7",
            "#6bfad8"
        )
    
    
    -- SVG generation
    VAR svg = "
    <svg xmlns='http://www.w3.org/2000/svg' width='" & sizeWidth & "' height='" & sizeHeight & "' viewBox='0 0 " & sizeWidth & " " & sizeHeight & "'>
      <style>
        .card-base {
          fill: " & baseColor & ";
        }
        .title {
          font-family: Segoe UI, sans-serif;
          font-size: 22px;
          font-weight: 600;
          fill: " & textColor & ";
        }
        .value {
          font-family: Segoe UI, sans-serif;
          font-size: 64px;
          font-weight: 900;
          fill: " & textColor & ";
        }
        .subtitle {
          font-family: Segoe UI, sans-serif;
          font-size: 14px;
          fill: " & subtitleColor & ";
        }
      </style>
    
      <!-- Background -->
      <rect class='card-base' width='" & sizeWidth & "' height='" & sizeHeight & "' rx='20' ry='20'/>
    
      <!-- Text -->
      <text x='30' y='60' class='title'>Title</text>
      <text x='30' y='120' class='value'>" & pctText & "</text>
      <text x='30' y='160' class='subtitle'>SubTitle</text>
    
    </svg>
    "
    
    RETURN "data:image/svg+xml;utf8," & svg
    

    Adding the SVG / HTML Measure into a Card

    Next, to use this measure I have been using it in the new card visual. Drop a card onto your dashboard – for the case of this code you will need to put any value into the Data field and then disable the callout value / label.

    Once added open the “Images” section on the card settings. Change the Image type to “Image URL” and select your new measure.

    Use SVG, HTML & CSS to enhance PowerBI reports

    Modifying for your own use case

    Once you have this in place you should end up with something like this

    Now you change them around, build anything as long you keep the main building blocks of the code for SVG rendering.

    Eventually you can end up with all sorts of cool things such as the below. These are then all animated with various methods.

    Use SVG, HTML & CSS to enhance PowerBI reports

    A further example

    This code for example animated the bar in the top right with a wave effect

    HTML_Wave_Bar = 
    
    VAR pct = Parameter1[Parameter Value]
    VAR pctText = FORMAT(pct * 100, "0") & "%"
    
    VAR numBars = 40                        -- Added: number of bars for progress
    VAR barsToFill = ROUND(pct * numBars, 0)   -- Added: how many bars to fill based on pct
    
    
    VAR fillColor =                          -- Added: conditional bar color based on pct
        SWITCH(
            TRUE(),
            pct < 0.2, "#E59EFB",
            pct > 0.8, "#F8FAB7",
            "#6bfad8"
        )
    
    -- Added: Generate multiple bar divs with animation and staggered delay
    VAR barHTML = 
    CONCATENATEX (
        GENERATESERIES(1, numBars, 1),
        VAR i = [Value]
        VAR isFilled = i <= barsToFill
        VAR barColor = IF(isFilled, fillColor, "#333")
        VAR height = IF(isFilled, "100%", "40%")
        VAR animation = IF(isFilled, "waveBar 2.5s ease-in-out infinite", "none")
        VAR delay = FORMAT((i - 1) * 0.10, "0.00") & "s"
        VAR animationDelay = IF(isFilled, delay, "0s")
        RETURN "
            <div class='bar' style='
                background: " & barColor & ";
                height: " & height & ";
                animation: " & animation & ";
                animation-delay: " & animationDelay & ";
            '></div>"
    )
    
    -- Dimensions increased for full bar display (added larger SVG size)
    VAR sizeWidth = 1280
    VAR sizeHeight = 200
    
    -- Added: Style definitions including animation keyframes for bars and fade-in for label
    VAR svghtml = "
    <foreignObject x='0' y='0' width='" & sizeWidth & "' height='" & sizeHeight & "'>
    <div xmlns='http://www.w3.org/1999/xhtml'>
      <style>
        .container {
          font-family: Segoe UI, sans-serif;
          width: 90%;
          height: 150px;
          margin: auto;
          display: flex;                     
          align-items: flex-end;
          justify-content: flex-start;
          gap: 4px;                          
        }
        .bar {
          width: 20px;
          border-radius: 4px;
          transition: height 0.3s ease;      
        }
        .percentage-label {
          font-size: 48px;
          font-weight: bold;
          color: " & fillColor & ";          
          text-shadow: 0 0 6px rgba(0,0,0,0.3);
          margin-left: 30px;
          align-self: flex-end;
          animation: fadeIn 0.5s ease-in;   
        }
        @keyframes waveBar {               
          0%, 100% { height: 60%; }
          50% { height: 100%; }
        }
        @keyframes fadeIn {                 
          from { opacity: 0; transform: translateX(-10px); }
          to { opacity: 1; transform: translateX(0); }
        }
      </style>
      <div class='container'>
        " & barHTML & "                   
        <div class='percentage-label'>" & pctText & "</div>  
      </div>
    </div>
    </foreignObject>
    "
    
    -- Wrap in SVG and return as image (same concept, but bigger canvas for wave bars)
    VAR svg = "<svg xmlns='http://www.w3.org/2000/svg' width='" & sizeWidth & "' height='" & sizeHeight & "'>" & svghtml & "</svg>"
    
    RETURN "data:image/svg+xml;utf8," & svg

    Aether Repository – Use SVG, HTML & CSS to enhance PowerBI reports

    I have added these base sets of code to my Aether repo. So feel free to grab, comment and play. As I create some new animations and visuals, I will look to upload those as well

    https://github.com/AetherAdv/dax_htmlbase_FO

    https://github.com/AetherAdv/dax_htmlbase_SVG

  • Enhancing Your DevOps Reporting in Power BI

    Enhancing Your DevOps Reporting in Power BI

    My role in Product Management requires me to use DevOps a fair amount, lets just say I always have it open in one way or another. And whilst there are a number of tools out there these days to manage backlogs, roadmaps and everything else in between, it turns out DevOps and PowerBI were all I needed. This blog post focuses on enhancing your DevOps reporting in Power BI.

    The challenge

    The main connector in PowerBI to pull data from DevOps is perfect for getting started but it only pulls a basic set of data.

    The default connector for example if we take the Work Items – All history endpoint gives you the following:

    • Area Path
    • Assigned To
    • Iteration Path
    • Work Item Id
    • Title
    • State
    • Work Item Type
    • Data
    • is Current

    And this is generally fine if you want a quick view. But if you need to review priorities, further information under those user stories. All those useful data points that can make a much more effective dashboard, we need to go further.

    Luckily we can expand this data out using APIs by simply using this first initial connection as a base.

    The function

    In PowerBI if we add the following as a function thats queries the DevOps API directly, meaning we can then use the Work Item Id to get those extra details

    In the below Ive set DEVOPSORG and DEVOPSPROJECT as parameters matching up with my Organisation name and Project Name.

    https://github.com/AetherAdv/powerbi_product_devopsfunction

    let
        FetchWorkItemSummary = (workItemId as text) as table =>
        let
            // Compose the request URL with API version
            EndpointUrl = "https://dev.azure.com/DEVOPSORG/DEVOPSPROJECT/_apis/wit/workitems/" & workItemId & "?api-version=7.1-preview.3",
            
            // Attempt to retrieve JSON data from Azure DevOps
            RawResponse = try Json.Document(VSTS.Contents(EndpointUrl)) otherwise error "No details for ID " & workItemId,
            
            // Verify expected structure
            HasFieldsSection = if Record.HasFields(RawResponse, "fields") then RawResponse[fields] else error "Missing 'fields' data for item " & workItemId,
            
            // Pull out specific fields
            TaskPriority = Record.FieldOrDefault(HasFieldsSection, "Microsoft.VSTS.Common.Priority", null),
            TaskDescription = Record.FieldOrDefault(HasFieldsSection, "System.Description", null),
    
            // Convert to a table format
            Output = Table.FromRecords({
                [Priority = TaskPriority, Description = TaskDescription]
            })
        in
            Output
    in
        FetchWorkItemSummary

    As part of this code Ive then collected the Priority and the Description, so instantly gaining more useful information for reporting.

    There are of course more fields that we can then collect if needed. Use this table below to identify the field reference and drop into the function.

    Field NameField ReferenceNotes
    TitleSystem.TitleShort name of the work item
    StateSystem.StateCurrent workflow state (e.g. New, Active, Closed)
    Work Item TypeSystem.WorkItemTypeType (e.g., Bug, Task, Epic)
    Created BySystem.CreatedByUser who created the work item
    Created DateSystem.CreatedDateWhen the item was created
    Changed BySystem.ChangedByLast user who changed it
    Changed DateSystem.ChangedDateWhen the item was last updated
    Assigned ToSystem.AssignedToCurrent assignee
    TagsSystem.TagsComma-separated string of tags
    Area PathSystem.AreaPathHierarchical area assignment
    Iteration PathSystem.IterationPathSprint or iteration it belongs to
    Effort / Story PointsMicrosoft.VSTS.Scheduling.StoryPointsOften used for estimation
    Remaining WorkMicrosoft.VSTS.Scheduling.RemainingWorkTypically used in Tasks
    PriorityMicrosoft.VSTS.Common.PriorityUsed for sorting/backlog
    SeverityMicrosoft.VSTS.Common.SeverityOften used in bugs
    DescriptionSystem.DescriptionFull rich-text description

    Why?

    This data now forms the basis of dashboards I and other stakeholders rely on when reviewing the backlog, keeping up to date on the road map and much more. Enhancing your DevOps reporting in Power BI means we can get the extra fields we need for stronger reporting capability.

    Coming Next

    Next up I will show some of this data in some of the dashboards I use today, how I’m continuously improving them to support better decision making and how you can also looking to use them in your own environment.

  • Updating PowerBI reports with PowerShell

    Updating PowerBI reports with PowerShell

    So this is probably the last PowerShell script for the moment. But this is where it gets interesting, we can now combine some of those scripts to make a quick and easy way of updating PowerBI reports with PowerShell.

    If you have the requirement where you have multiple instances of the same report across the same or different workspaces this script is for you!

    I had that requirement as part of Prism and again as things scaled up, this became a huge time saver. It also removed the potential of human error when moving parameters around, uploading to the correct workspace.

    Similar to the uploading new report script in my previous post, this one will pick up a pbix file then scan over your workspaces (based on when filters you apply). When it finds reports that again match your criteria, it will take a copy of the current parameters, update the pbix file and then load the parameters back in.

    Meaning, you have a PowerBI report uploaded to the service with your latest changes from a single source file, the parameters all remain the same as before, the script then refreshes to pull in the data based on those parameters and all good to go!

    As part of version control, I currently use a parameter to record the current version of my reports. This adds an extra benefit as I can then use this script to check if the reports are already on the expected version. Just in case the script is interrupted, we need to deploy on stages.

    I then add in the new version number as part of the script and this becomes a great way to track report versions when updating PowerBI reports with PowerShell.

    How it works?

    • Connects to Power BI Service using Connect-PowerBIServiceAccount.
    • Retrieves all Power BI workspaces using Get-PowerBIWorkspace.
    • Loops through each workspace and identifies reports whose names start with “AETHER”.
    • For each report:
    • Retrieves the dataset parameters.
    • Updates the first parameter’s value to a specified version if it doesn’t already match.
    • Overwrites the report in the workspace using a specified PBIX file ($FilePath).
    • Takes over the dataset to ensure permissions are set correctly.
    • Updates the dataset parameters.
    • Triggers a dataset refresh.

    Key things you can change

    • $DeployVer: The new deployment version to update the first parameter to (e.g., “2025Q1”).
    • $FilePath: The path to the PBIX file used for updating reports.
    • Parameter 0 is assumed to represent a version parameter (e.g., “2025Q1”)

    https://github.com/AetherAdv/powerbi_powershell_updatereports/upload/main

    # Connect to Power BI Service Account
    Connect-PowerBIServiceAccount
    
    # Set the deployment version to be used for updating parameters
    $DeployVer = "2025Q1"
    
    # Define the path to the PBIX file to be used for report updates
    $FilePath = "C:\Temp\myreport.pbix"
    
    # Define the conflict action for updating reports (e.g., Create or Overwrite existing reports)
    $Conflict = "CreateOrOverwrite"
    
    # Retrieve all Power BI workspaces
    $workspaces = Get-PowerBIWorkspace -All
    
    # Loop through each workspace
    foreach ($workspace in $workspaces) {
    
        # Get all reports in the current workspace with names starting with "AETHER"
        $Reportlist = Get-PowerBIReport -WorkspaceId $workspace.Id | Where-Object { $_.Name -like 'AETHER*' }
    
        # Check if any reports were found in the workspace
        if ($Reportlist) {
            Write-Host "Workspace: $($workspace.Name)" # Log the workspace name
    
            # Loop through each report in the report list
            foreach ($Report in $Reportlist) {
                Write-Host "  Report: $($Report.Name)" # Log the report name
    
                $JsonString = $null # Initialize JSON string variable
    
                # Retrieve the parameters of the dataset associated with the report
                $ParametersJsonString = Invoke-PowerBIRestMethod -Url "https://api.powerbi.com/v1.0/myorg/groups/$($workspace.Id)/datasets/$($Report.DatasetId)/parameters" -Method Get
                $Parameters = (ConvertFrom-Json $ParametersJsonString).value # Convert JSON response to PowerShell object
    
                # Initialize an empty array to hold parameter updates
                $UpdateParameterList = @()
    
                # Loop through each parameter and prepare the update list
                foreach ($Parameter in $Parameters) {
                    $UpdateParameterList += @{ "name" = $Parameter.name; "newValue" = $Parameter.currentValue }
                }
    
                # Check if there are any parameters to update
                if ($UpdateParameterList.Count -gt 0) {
                    # Get the current value of the first parameter
                    $currentparam = $UpdateParameterList[0].newValue
    
                    Write-Host "    Current Parameter 0 Value: $currentparam" # Log the current parameter value
    
                    # Check if the current parameter value matches the deployment version
                    if ($currentparam -ne $DeployVer) {
                        Write-Host "Version does not match. Updating..." # Log the update action
    
                        # Update the first parameter to the new deployment version
                        $UpdateParameterList[0].newValue = $DeployVer
                    }
                    else {
                        Write-Host "Version already matches. Skipping update." # Log if no update is needed
                    }
    
                    # Prepare the JSON payload for updating parameters
                    $JsonBase = @{ "updateDetails" = $UpdateParameterList }
                    $JsonString = $JsonBase | ConvertTo-Json
    
                    # Define the report name
                    $ReportName = $Report.Name
    
                    # Update the existing report in the workspace
                    New-PowerBIReport -Path $FilePath -Name $ReportName -WorkspaceId $workspace.Id -ConflictAction $Conflict
    
                    # Take over the dataset to ensure permissions are set correctly
                    Invoke-PowerBIRestMethod -Url "https://api.powerbi.com/v1.0/myorg/groups/$($workspace.Id)/datasets/$($Report.DatasetId)/Default.TakeOver" -Method Post
    
                    # Update the parameters of the dataset
                    Invoke-PowerBIRestMethod -Url "https://api.powerbi.com/v1.0/myorg/groups/$($workspace.Id)/datasets/$($Report.DatasetId)/Default.UpdateParameters" -Method Post -Body $JsonString
    
                    # Pause for 5 seconds to avoid API rate limits
                    Start-Sleep -Seconds 5
    
                    # Trigger a dataset refresh
                    Invoke-PowerBIRestMethod -Url "https://api.powerbi.com/v1.0/myorg/groups/$($workspace.Id)/datasets/$($Report.DatasetId)/refreshes" -Method Post
                    Write-Host "Refresh started." # Log the refresh action
                }
                else {
                    Write-Host "No parameters found for this dataset." # Log if no parameters are found
                }
            }
        } else {
            Write-Host "No reports found in workspace: $($workspace.Name)" # Log if no reports are found in the workspace
        }
    }
    
    # Log the completion of the script
    Write-Host "Script completed."