The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Coming at this from a database design perspective. I am accustomed to having the table as the fundamental record set, and then make a series of queries each with a descriptive name....and they all co-exist.
In Power BI I with a table, Addresses, with 1000+ records and about 6 fields
I made a query to create a StateCount field so now Query 1 there are 50 records with 2 fields, State and StateCount field - so far so good - this is used to create a Map visual of address per state.
Now I want to make another query of the table, Addresses, for Property Type count - same idea - 2 fields, State and PropertyTypeCount. There are 3 property type so assuming all 3 in each state this query is going to have 150 records....
My question is: where is the fundamental Addresses table now? When I look at it all I see is the first query of 2 columns. Does one need to dupe the fundamental table repeatedly to create a starting point for each query? Have relooked thru the guided learning and am not seeing this high level approach discussed so thought I would ask advice.
Possibly I am just not understanding the user interface but if one wants to make say 5 different queries off the same table how does one approach that efficiently?
Solved! Go to Solution.
In this scenario, did you import only one Address table into Power BI desktop, and then do modifications or create calculated table based on that table?
If so, please duplicate existing Address table for each query, then do shape and comine data on duplicated ones. You can just "Copy Table" and paste it in "Enter Data".
Regards,
In this scenario, did you import only one Address table into Power BI desktop, and then do modifications or create calculated table based on that table?
If so, please duplicate existing Address table for each query, then do shape and comine data on duplicated ones. You can just "Copy Table" and paste it in "Enter Data".
Regards,
thank you for the reply. It answers the fundamental question as to the difference between a database design versus Power BI.
As per my first post in a database 1 table exists forever and you make as many queries as you wish. With Power BI the query redefines the starting table permanently and so one must duplicate the table for each query.
I discovered that one can also duplicate the query itself - then undo some of the steps - and create new steps as a way to make a similar query fairly easily.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
116 | |
82 | |
75 | |
54 | |
48 |
User | Count |
---|---|
134 | |
124 | |
78 | |
64 | |
63 |