I have run into the same issue regarding the "No Such Column" message.
I thought that I read somewhere that this is a side effect of using the countd function in table calculations, but I have not gotten any legitimate feedback on the issue.
Tracy Rodgers can you possibly shed some light on this issue?
If using an extract, you might try removing/deleting the extract, and re-creating it before publishing to server. I've had issues where calculations have been modified, or I've changed something in the data, then published without my extract knowing that a change occurred. Hopefully what I am saying is making some sort of sense... anyway, re-creating the extract in cases like this has served me well. Similar to what is described here: "Ignoring calculated field, field is already defined by data source" Error | Tableau Software
No guarantees this will apply in your situation, but let us know what you find out.
Hi Matthew and David,
There are a number of different scenarios for the No Such Column error. Many of them were fixed with the release of 8.0.3 (refer to the release notes for this release here: Release Notes | Tableau Software) I would recommend upgrading to the most recent release (8.0.4). If the errors continue, please send the issue to our support team (Get to the Answer | Tableau Software)
Hope this helps!