Skip to main content

PowerBI–Limit the amount of imported data

For an Azure Fabric based data platform we are building I'm evaluating PowerBI as a possible reporting solution. My knowledge of PowerBI is almost non existant so there are a lot of things I learned along the way.

Yesterday I talked about the different data fetching strategies. Today I want to focus on how to limit the amount of data.

I explained yesterday that PowerBI can handle large amounts of data. This is good news but during development I want to work with a smaller dataset to limit the file size and gain some extra development speed.

Limit the amount of data

Let’s find out how we can get limit the amount of data in PowerBI.

Start by opening the Query Editor view in PowerBI by selecting Transform data from the Home tab:

This will load the Query Editor.

Here we need to create a new parameter that can be used as a limit value. Click on Manage Parameters and choose New Parameter:

We create a LimitRows parameter with a default value of 10:

Now that we have this parameter we can update our PowerQuery and introduce an extra step to limit our dataset.Therefore we open the Advanced Editor available in the Query pane:

Here we can update our query and implement the following logic:

  • If our parameter is less than or equal to 0 then return all the rows, otherwise
  • If our parameter is more than 0 then return that number of rows from the table

We change the existing query and introduce an extra step in the data pipeline:

    Click on Done to apply the updated query and introduce the extra step:


    Remark: This is a contrived example as our source is a JSON file but this can also be used when querying other sources(like a database).

    Popular posts from this blog

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

    Cache stampede: when our cache turned against us

    While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.