Forum Discussion
Split and append table to reduce data load?
No, that won't work that way. What you are doing just prevents having duplicate rows in two different tables (if you never load the first query that is). Essentially, the Append statement is still going to execute the query you specify for your historic data. What I would suggest is that you have your two queries. Load the first and second queries. Then disable Load for your first query (historic). Then, use the UNION function in DAX to create a New Table that UNION's your two tables together. In this way, you will only get updates when you refresh data but you will have a single table that appends both together.
No, that won't work that way. What you are doing just prevents having duplicate rows in two different tables (if you never load the first query that is). Essentially, the Append statement is still going to execute the query you specify for your historic data. What I would suggest is that you have your two queries. Load the first and second queries. Then disable Load for your first query (historic). Then, use the UNION function in DAX to create a New Table that UNION's your two tables together. In this way, you will only get updates when you refresh data but you will have a single table that appends both together.
I am trying to apply your solution, but there is a step unclear to me; if I disable the load of the first query, the new table generated with DAX UNION will not recognize the first table and fail. What am I doing wrong?