Forum Discussion
Resolver IRemove existing datasource - 2026 edition
Hello Irwan - thank you very much for your reply.
I solved my issue right about at the same time you were replying to me. As it turns out, it was one of the solutions from the older post, but I did not realize it earlier.
The model in question has a mix of tables configured for incremental refresh and those that are not, because they are too small to require that. When I changed the datasource on migration, and found that both old and new were in the published model, my first thought (which is suggested in that old thread) was that the queries for some tables still had the old source in them.
I looked at a selection of tables in the Query Editor, and found this not to be the case. Only the new source was in there. But I didn't inspect every table, and because of this, I did not notice that the QE, for whatever reason, was only showing me the tables that were not configured for IR. The queries for the IR tables all still had the old source in them, but those tables were not listed in the QE when I did my inspection.
I didn't notice this until I subsequently opened the published model in TE3 and inspected the query sources there. I updated the connect string for all affected tables in TE3, saved that out to the service, and was good to go from there.
I don't know why Desktop did not update the IR table sources when I changed the datasource in the file, but that is a mystery for another day.
Thank you again for your reply.
Super Userhello markmsc
i might be misunderstood, but in Power BI Service, i assumed you are doing in workspace then i think it should be possible.
then you will be directed into another option with open semantic model
from here, the view will be power query like transform model in power bi desktop.
change viewing (default) into editing to change any m-code.
Hope this will help.
Thank you.
markmscHello Irwan - thank you very much for your reply.
I solved my issue right about at the same time you were replying to me. As it turns out, it was one of the solutions from the older post, but I did not realize it earlier.
The model in question has a mix of tables configured for incremental refresh and those that are not, because they are too small to require that. When I changed the datasource on migration, and found that both old and new were in the published model, my first thought (which is suggested in that old thread) was that the queries for some tables still had the old source in them.
I looked at a selection of tables in the Query Editor, and found this not to be the case. Only the new source was in there. But I didn't inspect every table, and because of this, I did not notice that the QE, for whatever reason, was only showing me the tables that were not configured for IR. The queries for the IR tables all still had the old source in them, but those tables were not listed in the QE when I did my inspection.
I didn't notice this until I subsequently opened the published model in TE3 and inspected the query sources there. I updated the connect string for all affected tables in TE3, saved that out to the service, and was good to go from there.
I don't know why Desktop did not update the IR table sources when I changed the datasource in the file, but that is a mystery for another day.
Thank you again for your reply.