Skip to content

Column with None values becomes "All" when publishing a workbook using the TSC Python client #1711

Closed as not planned

Description

@MeghanaShivamurthy

Describe the bug

When publishing a workbook to Tableau Server using the Tableau Server Client (TSC) Python library, a column in the underlying table that contains None values is being converted to the string "All".
This happens only when publishing via TSC.
Publishing the same workbook manually to Tableau Server preserves the None values correctly.

Expected behavior
When publishing a workbook using the TSC client, column values that are None should remain unchanged—exactly as they do when publishing manually to Tableau Server.

Actual behavior
A datasource table includes a column with None values.
When publishing the workbook using TSC (server.workbooks.publish()), the None values in that column are changed to "All".
No transformation or custom handling of values is applied in the Python script.

Versions
Details of your environment, including:

  • Tableau Server version - 2025.1.7 (20251.25.0825.1650) 64-bit Linux
  • Python version - 3.9
  • TSC library version - 0.15.0

To Reproduce

  • Create a workbook with a datasource table containing at least one column with None values.
  • Publish the workbook using TSC:
  • server.workbooks.publish(wb_item, file_path, mode)
  • Open the published workbook on Tableau Server.
  • Observe that the original None values have been replaced with "All".

Results

This issue leads to incorrect data representation in the published workbook and may cause:

  • Misleading data displays
  • Filters not behaving as expected
  • Broken calculations relying on None values
  • Confusion or incorrect interpretation for end users

NOTE: Be careful not to post user names, passwords, auth tokens or any other private or sensitive information.

Activity

  1. jacalata commented on Nov 20, 2025

    @jacalata
    Contributor

    Hi Meghana, thanks for the report. When you say this does not happen if publishing manually, do you mean you published through the web UI, or you were using a script that called the publish API directly?

    cheers,
    Jac

  2. MeghanaShivamurthy commented on Dec 22, 2025

    @MeghanaShivamurthy
    Author

    Hi Jac,

    Manually meant through the web UI through upload workbook option in the UI. Could you please help resolve this issue?

    Thanks,
    Meghana Shivamurthy

  3. bcantoni commented on Apr 8, 2026

    @bcantoni
    Contributor

    @MeghanaShivamurthy are you still having this problem? I tried to reproduce with this simple .CSV file with some nulls:

    id,name,category,status
    1,Item A,Category1,Active
    2,Item B,,Active
    3,Item C,Category2,
    4,Item D,,Inactive
    5,Item E,Category3,Active
    

    Then a simple workbook in Tableau desktop does show the Null values as expected:

    Image

    And then when published to Tableau server via TSC I'm getting the same results:

    Image
  4. github-actions commented on Jul 24, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.

  5. jacalata commented on Jul 30, 2026

    @jacalata
    Contributor

    I also wasn't able to reproduce this. I tried the values "", "None", and Python None. To get further, could you share (1) the exact code that constructs the workbook/datasource before server.workbooks.publish (in particular how the None-bearing column is written into the extract), and (2) a datasources.download of the offending workbook's data source so we can see what actually landed on disk versus what the viz renders? A screenshot of the viz showing "All" alongside the row where the data source says None would also help distinguish "data mutated on publish" from "viz rendering a null-in-filter as the word All".

  6. github-actions commented on Oct 7, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.

  7. github-actions commented on Oct 22, 2026

    @github-actions

    Closing due to inactivity. If this is still relevant, please reopen or file a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugneeds investigationIssue needs to be looked at by TableaustaletriagedReviewed by a maintainer; leave closed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions