Skip to main content

Exporting Data In Power BI

Power is like the year 2020, full of surprises. You must be wondering what did it do again! Well, it really surprised me the other day. When I was exporting data from Power BI, I've faced a very unexpected result, and this post is about that result. And of course, about the solution to that.



This is my data table. As you see, the table has 23,443 rows. On the report view, I have created a table visual by taking all the 23,443 rows and all the columns of this table. And there is no explicit filter on that visual like report level, page level, or visual level filter. After that, I have clicked on Export data option. That option creates a CSV file that you can save on your computer.


And this is the CSV file that Power BI has created.




In the beginning, everything seemed quite normal. But when I kept scrolling down, I have noticed that I have much less row than I was supposed to have. When I was creating this file I was hoping to find all the 23,443 rows on the visual. But 167 is not even close to 23,443. It seems like when we use Export data option, it might only take some random rows, and it's not top 167 or bottom 167. Power BI chose some rows to import completely randomly.


The solution to this problem is using Copy table option. After copying the table, you can directly paste it into Excel. If you don't need to copy the whole table, you can only copy the columns that you need and paste them. Copy table option is available at Data view at Power BI Desktop. And on Power Query, the same thing can be done by clicking on Copy Entire Table option. 


For experimental purposes, I have used the Export data option with other tables and columns as well. It doesn't always disappoint you, sometimes it takes an entire table, sometimes not. That's why it's always better to check the result before taking the next step.

Comments

Popular posts from this blog

Manipulating Grand Totals with ISINSCOPE in Power BI

ISINSCOPE function was introduced in with November 2018 Power BI update. We can say it's a very young player in the game, but it's definitely magic. It can be used to manage lots of issues related to hierarchies, but in this post, I'm going to focus on manipulating the grand total line with it.  This is my budget forecast table. The budget forecast that you see for every month is not the forecast for every month, but it's the forecast for the whole year. The budget forecast for 2020 has changed every month. That's why we have different numbers for every row. Below you see the table visual with the year-month column and a measure that shows the values for every month. The thing that I want you to pay attention to is the total line. I wanted to see the last month's value for the total line and this is the measure for that.  This measure calculates this: If the year-month column has one value then take the average of that value. If it doesn't have one value, li...

How to Add Flags to Power BI Reports

Adding flags to Power BI Reports might be easier said than done. If you have a dataset which contains data of various countries, adding country flags looks cool. The process to do it, on the other hand, might be compelling. Now I am going to share with you the obstacles I  have faced during the process and of course, how I overcame them. First I made an excel list of countries that my dataset has. Then I have downloaded to my computer all the flags I need from Wikipedia and converted them to Base64 link via an image encoder website  base64-image.de  and added those links to my excel file, which looks like this: After I added my excel file to Power BI, I converted the data category of URL column from 'uncategorized' to 'image URL', which might be a small step for you but it's a big step for the success of the flag operation. Then I created one to many relationship with DimLocation table and chose 'both' as filter direction, so that I can filter from both t...

Solving Data Type Conflicts in Power BI and SQL

Whether we like it or not, error messages are part of our lives. The other day, I faced one of those little horrid yellow messages. For me, it's impossible to stay chill when I see that message. For a second, I feel alarmed and panicked. Let me show you what I'm talking about. The first column is the customer code, quite self-explanatory. The Registration Date column shows the date when the customer registered to my shop. The First Sale Date column shows the date when the customer bought something for the first time. And this is what I'm trying to see in the Sales Day column: If Registration Date and First Sale Date are the same, meaning customer bought something at the same day customer registered to my shop, print  "First Day", otherwise show the data of First Sale Date column. But computer says no! It says "Expressions that yield variant data-type cannot be used to define calculated columns." If I need to translate it in simplified English, it means: ...