I have tried the same steps, and see the same results as you. The colours displayed for my clustering in server has reverted to default, and are different from the ones on Desktop.
This looks to be a bug (or there is a reason Tableau has decided to implement this, though I cant think why)
I have checked the bug list and cant see this as having been reported.
and you can submit a bug report here
All the best
This does seem a bit odd. Now here is a quick fix for the problem. Once you create your clusters drag the newly create clusters to the data pane to create a group. Example below:
Now drag the newly create group back on to the color shelf and assign a custom palette and then save your workbook.
Attached is an example of .twbx were I did the above and the color palette changes do stick. I would definitely log a case with support and reference this thread in the support case.
Looking through the xml the original ad-hoc clusters are just aliases. Once you give them a name, by placing them on the data pane, you can assign a color palette to them.
Absolutely worked. I do have a ticket in with support already, so I'll forward your workaround to my adviser.
Thank you so much!
P.S. Don't forget to update this thread with what support tells you.
Gerardo Nailed it!
I am the Support Engineer that picked up this case from Andrea - and this explanation from Gerardo describes exactly what is going on, as well as the solution.
When a Cluster is created in Tableau Desktop v10, this field exists as an 'ad-hoc' calculation. This calculation is then 'converted' to a standard calculation when the field is dragged from the view to the data pane. This 'non-persistent' color assignment is the expected behavior for ad-hoc calculations.
The following resource has some additional information on some unexpected behavior that has been noted when working with ad-hoc calculated fields:
Custom Color Palette Does Not Save with Ad-Hoc Calculation