sourceName and sourceLineageTag should be mutually exclusive.

[kleigh]

I have a report that is connected via DirectQuery to the main model. Automatically adding new tables is turned off, so I am manually adding a table from the model. On saving my changes, I am met with the error "sourceName and sourceLineageTag should be mutually exclusive."

There are currently zero search results for this message so I'm unsure how to tackle this?

[C4YNelis]

Since this is the only result coming up in any searches, I'll add to this topic, just in case anyone else encounters this same problem.

I too received the same error when trying to remove tables from a mixed storage mode model, which connects to several semantic models in the service. I had automatically add new tables disabled, but they ended up in my report all the same. When trying to remove them (and others), I got this error.

My first thought was dependencies in measures on one or more of the tables I wanted to to remove, but checking with INFO.VIEW.MEASURES() as a calculated table didn't give me any dependencies.

In the end I removed them with Tabular Editor 2, which worked just fine and which was indeed able to save to the model.

Cheers

[Anonymous]

Hi @kleigh ,

Can you please share some more detail information about this issue? They should help us clarify your scenario and test to troubleshoot. (e.g. data source type, any structure change applied on the data source)

How to Get Your Question Answered Quickly  

Regards,

Xiaoxin Sheng

[kleigh]

After doing more tests, I have found a solution:

There were some measures defined against a different table that was not loaded. So:

1. Use Enter Data to create a dummy table with the same name.
2. Delete the measures.
   1. At this point, the dummy table may rename itself to add a (2) and move position in the table list
3. Delete the dummy table.

To be clear:

• These were measures defined in the report itself, not the main model. They were leftovers from previous work.
• The measures were broken, but fixing them in DAX View was not enough to remove the error.
• Loading the table the measures were defined against also fixed the problem. Since I didn't want the table loaded, I used the other method.
• Simply creating the dummy table was not enough. The measures had to be removed for this method to work.
• I used DAX view to "Define all measures in this model", this helped find the measured
  • External measures are not at fault here. I pasted the definitions into a text editor and used the regex ^.+EXTERNALMEASURE.+$ to find and remove these, leaving behind the locally defined ones. This made it clear where all the measures were coming from.
• When cleaning a report by removing unused tables, be sure to remove all local measures first!