Skip to main content

Power BI Journey: Blog #4



In this blog, I will be changing my approach to how I write the blog. In the previous blogs on Power BI, I was simultaneously doing what Alex is doing in Power BI and then, whenever I encounter issues, I will be writing it directly in the blog and then continued where I left off with the video once I am done. Here, I will watch the video first, take note of important keywords and lessons that Alex emphasizes, and then replicate what he did on the video.


This lesson focuses on DAX or Data Analytics eXpressions. Based on what I understood on the video, DAX can be likened to the formulas associated with MS Excel. And, since Power BI is also a Microsoft product, there are DAX that are similar, if not, the same with what can be found in MS Excel (One example is the IF expression in Power BI).


In this exercise, the process of using DAX was explained starting with creating "New Measure" and then using various DAX to be able to visualize the intended outcome in a table. For example, if we want to visualize the Count of Sales, we can use the expression, COUNT, :

Count of Sales = COUNT('Apocolypse Sales'[Order ID])

This expression counts how many rows are under the Order ID column of the table Apocalypse Sales.

Next, we added a Customer column in order to count the number of orders made by each customer.



Another DAX that was used is SUM. In this particular visualization, we would like to know the total number of sold items for each product.


We can also use mathematical operations for DAX. In this particular visualization, we would like to know the profit made from each customer.


Notice that on the Profit expression:

Profit = (SUM('Apocolypse Store'[Price])-SUM('Apocolypse Store'[Production Cost]))*SUM('Apocolypse Sales'[Units Sold])

we used PEMDAS to calculate the profit for each customers. Notice also its similarity with Excel Formulas.

The next lesson that was discussed was how to create new columns using DAX. In a way, this is like creating one formula at the top most cell and then dragging it down towards the end of the table in MS Excel. In Power BI, this is more efficient using DAX. We click Home > New Column > write the DAX associated with the column. Here are some examples.

Using WEEKDAY:


Using IF:

Notice that when we are using DAX to create new columns, we are using Power Query editor.

Basically, DAX is equivalent to MS Excel Formulas but is more efficient when it comes to executing it on a given table. 


Comments

Popular posts from this blog

Privacy Policy of ShinStats: descriptives calc

Privacy Policy Shin Nix built the ShinStats app as an Ad Supported app. This SERVICE is provided by Shin Nix at no cost and is intended for use as is. This page is used to inform visitors regarding my policies with the collection, use, and disclosure of Personal Information if anyone decided to use my Service. If you choose to use my Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that I collect is used for providing and improving the Service. I will not use or share your information with anyone except as described in this Privacy Policy. The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which are accessible at ShinStats unless otherwise defined in this Privacy Policy. Information Collection and Use For a better experience, while using our Service, I may require you to provide us with certain personally identifiable information. The information that I request will be retaine...

SQL Journey: Blog#10

So far, we are only "reading" from a given database or table using the SELECT command of SQL. In today's lesson, we will now start "writing" into a given database using the UPDATE and DELETE commands. Challenge: Dynamic Documents Given data: CREATE table documents (     id INTEGER PRIMARY KEY AUTOINCREMENT,     title TEXT,     content TEXT,     author TEXT);      INSERT INTO documents (author, title, content)     VALUES ("Puff T.M. Dragon", "Fancy Stuff", "Ceiling wax, dragon wings, etc."); INSERT INTO documents (author, title, content)     VALUES ("Puff T.M. Dragon", "Living Things", "They're located in the left ear, you know."); INSERT INTO documents (author, title, content)     VALUES ("Jackie Paper", "Pirate Recipes", "Cherry pie, apple pie, blueberry pie."); INSERT INTO documents (author, title, content)     VALUES ("Jackie Paper", "Boat Supplies...

SQL Journey: Blog #14

I am now on what Alex the Analyst would call the advanced SQL queries. First off, the Common Table Expression or CTEs. Based on what I understood in the video, CTEs is similar to a function or class in Python which you can call out. It is just how I felt when I first encountered this expression. Now, in this particular case, I tried to replicate what Alex is doing but also not copying the codes that he is using. I am just simply trying to understand what the expression that was used (which starts with WITH) and then observe how he used the said expression. This was my code. Now this code, resulted in the following error. Msg 8156, Level 16, State 1, Line 84 The column 'EmployeeID' was specified multiple times for 'CTE_Employee'. What does someone do in this day and age if we encounter something that bogs us down? We go to the internet especially to AI tools to aid us out. And, apparently, these tools will really come in handy. It stated that the error occurred because I...