Skip to main content

PowerBI - Combine multiple column inside the same chart

 Let's assume that we have a table with the below heather:

EmployeeID | Location | Skill1Level | Skill2Level | Skill3Level | Skill4Level

The Location field contains the name of the city where he is based and each skill level is a value between 1 to 5.

What we want to achieve

We need to show in a chart what are the skills level in a specific location. Additional to this, we need to have a line chart that shows all the skills cross locations and the ability to specify what skills and location to show on the charts (Slicer)

Problem

Except for the Splicer, we could drag and drop all the columns inside the Values of each chart to get what we want. The input table has data already pivoted and makes it almost impossible for us to generate and make the Slicer to work.

Solution

I found multiple solutions, but the one that was recommended by one of my co-workers was to do an unpivot to the table. The solution is simple, clean and you end up with your input data in a format easy to manage and manipulate. In the Applied Steps of your table you shall add the following step:

= Table.Unpivot(#"NameOfPreviousStep", {"Skill1Level", "Skill2Level", "Skill3Level", "Skill4Level"}, "SkillName", "SkillValue")

The output is a new structure of the table that looks like that:

EmployeeID | Location | SkillName | SkillValue

For each employee, you have multiple rows (one row per skill). From now generating charts and slicers where you use the employee location is easy


Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too