Your workbook has duplicate named fields, some locked, some editable with terrible names like [Sales copy (6) Fred edit final]
to distinguish from [Sales final DoNotUse]
. This is incredibly confusing to work from and distances yourself from the single source of truth we all desire.
Eventually you will need to fix this issue so that the workbook can be developed efficiently and this will waste resources.
The good news is it’s easy to prevent. Let’s get stuck in.
Firstly, how did we even get to this mess? What led us to get here is often an unclear order of operations to update a published datasource. It’s easy to do and I’d expect many beginner users to fall into this trap.
So let’s say we have a Tableau workbook on Cloud/Server and we are tasked to update the datasource. We need to switch it over to look at a slightly different table in our database or update the custom SQL.
So we open the workbook in Desktop, edit the datasource and then republish. All is well and our datasource is updated.
WRONG. DO NOT DO THIS.
You have just published the datasource, but along with it all of the calculations in your workbook. These calculations are no longer a property of the workbook but instead a property of the published datasource. They are no longer editable in the workbook.
The calculations must stay a part of the workbook if you want them to remain editable.
Once you’re in this mess, it is fixable and I will now walk you through it.
Create local copy of datasource
4.1 You should now have a new datasource:
In the data pane, filter for calculations
That wasn’t very fun was it?
So what can we remember to not get in this pickle again. Put simply:
If you need to edit a datasource, open Tableau Desktop, connect to the published datasource, make your changes and publish back to Server/Cloud. No need to have the workbook that USES the datasource open.
Your Tableau developers or future self will be thankful, or in other words, you’ll be minimising technical debt.
Written on May 7th, 2025 by Chris Meardon