Forum Discussion
Appending with Direct Querry error
Anonymous,
I can reproduce this issue if I turn on composite models in Power BI Desktop.
In your scenario, please disable the composite models option, then open a new PBIX file, re-connect to the excel data source, repeat the steps in situation 1 and you will be able to apply change.
In addition, please check PG's response about this issue."We have received several reports of issues similar to this. The underlying issue is that the query is being mistakenly classified as DirectQuery rather than import. We're making some improvements to this such that this does not happen, but they aren't available just yet."
Regards,
Lydia
Anonymous,
I am unable to reproduce this issue in Power BI Desktop september version 2.62.5222.761. Does your excel file contain other data source? Could you please check the connection mode in the PBIX file?
In addition, instead of appending query in query editor, you can use UNION DAX function to append tables.
Regards,
Lydia
Thank you, I know UNION will work. I actualy just start a new PowerBI and import the data again. Here's what I found:
_ Situation 1: When Import query1 and query2 and append them sucessfuly in Power Query, I uncheck the Enable Load of the query1 and query2 then Import them into the model. Now, it shows that message.
_ Situation 2: After I successfuly append them in Power Query, I import all 3 dataset. It works, now I comeback to Power Query and uncheck the Enable Load of query1 and 2 again. It works and doesn't show the error anymore.
I don't know why this happens?
Duc
Anonymous,
I can reproduce this issue if I turn on composite models in Power BI Desktop.
In your scenario, please disable the composite models option, then open a new PBIX file, re-connect to the excel data source, repeat the steps in situation 1 and you will be able to apply change.
In addition, please check PG's response about this issue."We have received several reports of issues similar to this. The underlying issue is that the query is being mistakenly classified as DirectQuery rather than import. We're making some improvements to this such that this does not happen, but they aren't available just yet."
Regards,
Lydia