<sigh> no. unfortunately you are not. This is an issue someone else actually reported and I currently do not have a good answer for it. This is due to the way the data is loaded in the tool when using a BWSX file. IT works if you give it a source server, and a target server. The tool picks up the dashboard object from the webservice and all is good.

When you use a BWSX file, it opens the file and takes the 'dashboard' element (which has the same structure as the webservice) and deserializes it to an object to use in the tool interchangeably with the rest of the code as if it came from a webservice. The issue is that this deserialization seems to not work with an embedded datatable inside the BWSX file. Something to do with the namespace and the data which is in the bwsx does not get into the object. Since the xmlserializer is a very general object, I have not found a way to make it also deserialize the datatable correctly with the rest of the object, so I am a bit stuck on that one.