OMG -Andy, I feel really dumb; I just realised that kriebela = Andy Kriebel. D'oh!
Is that the same as "panties in a bunch?" Thanks for the terrific discussion here and on LinkedIn.
This works great! Thanks for the post!
Has anyone had any successful results adjusting the XML in version 6.0?
Yes, but I do not have methods that work in every case, only for the workbooks that I create, that are known quantities, can I get reliable results with my XML editing scripts. When I try to programmatic edit a workbook that someone else made, sometimes, my edits fail, because of different styles in creating workbooks create different XML. If my intention is to modify the XML of a workbook, when I am creating the workbook, I will be mindful of every option I am setting and consider how each click or drop will effect the underlying XML. This way, when I go to edit the XML after creation, I am aware of the settings in the XML and can avoid corrupting my work. It is still a hack and not supported to edit the XML directly, but maybe some others have methods of editing the XML that is more resilient to different styles.
Reiterating what Joe says - editing XML is sometimes hit-and-miss. Hacking your own workbooks on-the-fly is fine (but remember to back everything up). It's largely a trial-and-error process. The reason that automating is so difficult is because Tableau Desktop doesn't create consistent XML for every design choice you make. For example, the XML that describes filters is different depending on whether it's on a dashboard or view, or whether you change a default filter setting.
It's important to say that Tableau Desktop can do whatever it wants with its XML - it only needs to serve the Desktop application. If it stops hackers like myself and Joe, that's our problem, not Tableau's!