Forum Discussion

CahabaData's avatar
CahabaData
Memorable Member
10 years ago
Solved

same table, several queries

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 c...
Need Help
  • v-sihou-msft's avatar
    v-sihou-msft
    10 years ago

    CahabaData

     

    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,

v-sihou-msft's avatar
v-sihou-msft
Microsoft Employee
10 years ago

CahabaData

 

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,

CahabaData's avatar
CahabaData
Memorable Member
10 years ago

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.