Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi,
Can we create new table with only particular columns from exsting query tables?
e.g. All existing tables have exact same format and wanna take particular 2 columns only from each existing tables and append all into 1 new table.
Of course I can do Append all tables as new first and delete other columns but the thing is this taking too much file size space and loading time, so I only wanna get necessary columns at the beginning.
1 more question,
If I select and copy those 2 columns and create new table and manually paste, then still connected to existing dataset?
if new data comes, then this new created table also reflect new data automatically?
Solved! Go to Solution.
Hi @jeongkim
Your DateTimeZone column has very high cardinality, which can significantly increase your model size. Consider removing the timezone and seconds if they aren't needed. To further reduce cardinality, you can also split the column into separate date and time columns.
Also, experiement with using DAX instead of append in the query editor to create a new table from already laoded ones.
New Table =
VAR tbl01 =
SELECTCOLUMNS (
tbl01,
"Desired Column Name1", tbl01[column1],
"Desired Column Name2", tbl01[column2]
)
VAR tbl02 =
SELECTCOLUMNS (
tbl02,
"Desired Column Name1", tbl02[column1],
"Desired Column Name2", tbl02[column2]
)
RETURN
UNION ( tbl01, tbl02 )
DAX expressions like UNION() are evaluated in memory after the data model is loaded, whereas Power Query transformations happen during the refresh process, which can be more time-consuming, especially for large datasets and/or slow data sources. Also, PQ appends require reshaping and reloading the data before it lands in the model. The DAX method skips that extra step and works with what's already loaded.
Hi @jeongkim
Your DateTimeZone column has very high cardinality, which can significantly increase your model size. Consider removing the timezone and seconds if they aren't needed. To further reduce cardinality, you can also split the column into separate date and time columns.
Also, experiement with using DAX instead of append in the query editor to create a new table from already laoded ones.
New Table =
VAR tbl01 =
SELECTCOLUMNS (
tbl01,
"Desired Column Name1", tbl01[column1],
"Desired Column Name2", tbl01[column2]
)
VAR tbl02 =
SELECTCOLUMNS (
tbl02,
"Desired Column Name1", tbl02[column1],
"Desired Column Name2", tbl02[column2]
)
RETURN
UNION ( tbl01, tbl02 )
DAX expressions like UNION() are evaluated in memory after the data model is loaded, whereas Power Query transformations happen during the refresh process, which can be more time-consuming, especially for large datasets and/or slow data sources. Also, PQ appends require reshaping and reloading the data before it lands in the model. The DAX method skips that extra step and works with what's already loaded.
Pls also 1 more question,
I recently added another column into input files in the same data table.
If I duplicate the data table in query and add column 'B-a' with blank value into Week 1~5,
no issue to append data set but it takes too much modeling size and hard to change any code due to loading time.
As you mentioned, can we do it in dax like 1 dax data table for Week 1~5 adding 'B-a' column and another dax data table for Week 6 ~ 10 and another dax data table to append W 1 ~ 10? without duplicating query?
Or any better idea pls?
each week data is split each file by file
Thanks it's really good to know.
'Consider removing the timezone and seconds '
Where did you check my data has timezone? and how can I remove it?
'you can also split the column into separate date and time columns'
How does it work differently with separation and without separation? while the same text still would be there.
Hi @jeongkim
That globe map with clock is a symbol for datetimezone. There's also +00
This is a pretty good blog that explains how VertiPaq compresses data - https://www.microsoftpressstore.com/articles/article.aspx?p=2449192&seqNum=3
Hello @jeongkim ,
for your second question that if you select and copy then pasted it in a new table, no it won't update since its not anymore connected to the datasource.
well the best approach is it to be done in the datasource if available, else it should be appended as you mentioned
Proud to be a Super User! | |
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
84 | |
76 | |
73 | |
42 | |
36 |
User | Count |
---|---|
109 | |
56 | |
52 | |
48 | |
43 |