I am getting the following stubborn error in an SSRS 2012 report:

Deploying report 'abc'.
Warning : The tablix 'xyz' contains an invalid DataSetName (Expected: ‘DataSet1’; Actual: ‘DataSet2’). The DataSetName of the inner data region or group must be the same as the DataSetName of the outer scope, unless a relationship is specified on the inner scope or on the dataset.

When looking through the visual studio GUI, the dataset name is correct, so the GUI shows nothing that would merit this warning. What is the best way to resolve this?

  • The format here is to submit a question. Then answer it separately...please edit this. – Thronk Oct 8 '15 at 15:13
  • 1
    Thank you. I am new to this forum, and have made the change you requested. – BI Developer Oct 8 '15 at 15:19
  • welcome to the forum! Lots of great contributors here. – CleanFill Oct 8 '15 at 15:41

I found a solution, so am posting for others to benefit.

The tablix receiving the warning was a tablix nested inside of another tablix. I had checked and rechecked that nested tablix, and nothing in the Visual Studio GUI was amiss. It was reporting the correct dataset.

Finally I resorted to opening up an XML editor and opened the RDL file, and sure enough, the XML file had the wrong dataset in the XML.

It was in the definition of the tablix, at this point:


The solution was to delete the


line from the XML entirely, because a nested tablix should not specify a dataset name, because by definition a nested tablix must use the dataset from the outer tablix.

The reason why this warning had come about was because originally I created the tablix as a standalone tablix, so it did have a dataset. After some report changes, I copied and pasted the tablix into another tablix. At that point, apparently, visual studio kept the dataset name in the paste, but did not support changing it from the GUI.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.