Yes - you should be able to do a data source extract refresh. What is the data source, Tableau version, database driver version and is this desktop or server?
You might want to initiate a case with Tableau Support as well since it could take them a few days to set up time to assist and this may only be able to be resolved with assistance from support.
The calculation in question is a Row-Level one --
those only contains datasource fields, other row-level calcs
(including FIXED LOD expressions) and simple operators.
Tableau materialises row-level calculations (including FIXED LODs)
when performing the initial extract build and the subsequent refreshes
(including the incremental ones). If a row-level calc has been introduced
after initial extract had been made, the incremental refresh would fail.
Other types of calculations -- Aggregates (INCLUDE/EXCLUDE LODs, too)
and Table Calculations -- are not materialised in the extract,
so there is no problem with them to be created / modified ad-hoc.
Hope this could help understanding.
I don't believe FIXED LODs are materialized at this time, otherwise we wouldn't be able to change the results with context filters. Have you seen something different?
Sent from my iPhone
The data source is Google BigQuery and it's on Tableau Desktop 9.3.4 (I think). I will consider getting in touch w/ Tableau support next time. In the interim I just re-did the entire extract. Time consuming, but I could get a working solution faster than waiting for Tableau to respond.
I have used Fixed LOD calculations but not in the field that it is complaining about. I don't necessarily understand why the client would perform the FIXED LOD calculations on the back end instead of doing it in the client, especially when it seems like they are doing it for the INCLUDE and EXCLUDE forms. Furthermore, it doesn't make any sense to me at all why adding an additional column to a table would affect a row-level calculation for another field. The new field doesn't match the name of any of the previous fields so it shouldn't clash with it in any way. It's just an additional vector of data. It makes absolutely no sense to me why this would cause a problem.
I suppose a work around would be to add this field to a new table along w/ only the other fields I'd need to do some data blending client side, but that is really frustrating.
Jonathan, you're right.
FIXED LODs are out of question,
since they're aggregate subqueries
joined back to the main select.
Sorry guys, I totally missed the point.
I ran into the same issue now while doing an incremental refresh and saw this question posted. Were you able to resolve this issue? Does anyone else have a solution for the problem?