PBI Desktop creating extra tables on refresh from Semantic Model

[FabricNZ]

Hello, I have an interesting problem that is currently with MS support with no progression yet, so thought I'd log here incase people have seen it.  PBI Desktop -> Fabric Semantic Model.  Three simple tables. For example, let's call the tables A,B & C.  The connection is direct query. I hit refresh and it creates duplicate tables in the PBI model, so now I have tables A, B & C and A 2, B2 and C2 and everything breaks. The SM is fine. It refreshes against the warehouse, discovers new columns, etc.  I believe, unless someone has done something with it, that the SM is as it has been for a long time (yes, something could have happened). But now, I can't refresh and pick up on new columns in PBI.  Everything breaks, relationships, 100s of measures, etc.  I look at the TDML and see....  The interesting thing is that table A2 picks up on all of the new columns in the SM.  It is like the existing table in the PBI model is pointing to something wrong.  Without a refresh, the data comes through and works.  The SourceLineageTag is different for both Table A and A2.  Very very strange. MS support is puzzled, but it is being escalated to product support. As said, thought I'd throw it out here.

createOrReplace

table A

lineageTag: 17b5dd18-1fc8-4968-8461-465b17244455

sourceLineageTag: d3a2fb22-4fe7-4748-aeaa-d496dc7c38de

createOrReplace

table A2

lineageTag: b9170bff-bf64-46bc-9220-f8e1b14ed4ff

sourceLineageTag: 99327874-aec8-4d85-90f1-d0c98ee8bcf3

Thank you

[FabricNZ]

Thank you.  I'll accept as the solution as that is the path I had started on today by exporting to a Project file and then editing the definitions, matching the tags.  I did try removing the connection but that broke more 🙂  Do you have a better way of aligning the SourceLineageTag than editing definition files?

[Akash_Varuna · Accepted solution]

Hi @FabricNZ This issue occurs due to mismatched lineage tags between Power BI Desktop and your semantic model, creating duplicate tables on refresh. To resolve, check and align the SourceLineageTag in your semantic model and Power BI. You can also try removing and re-adding the connection in Power BI Desktop. Avoid refreshing until a fix is in place to prevent breaking relationships and measures.