GeezerVison is showing github.com — Document filter special characters, wildcards and case sensitivity by jacalata · Pull Request #1906 · tableau/server-client-python
Conversation
jacalata
commented
Nov 10, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
Summary
- Documents that a comma in a filter value fails with error 400065 and shows the
* workaround with a client-side check.
- Documents that
&, :, [ and ] match as written. From REST API 3.7, TSC URL-encodes the query string, so & is safe. Earlier versions do not encode it.
- Records that
Equals treats * as a wildcard at the start, end and middle of the value on name fields, although the REST API documentation describes wildcards only for like and does not say which versions support the behavior.
- Documents
CaseInsensitiveEquals and that Equals ignores case for workbook, data source, project and user names but is case-sensitive for group names on Tableau Server.
- Adds an example of the
In operator, including that a value containing a comma is split and does not match.
- Adds a section on view filters (
vf), which use different value rules, and notes that TSC sends an ampersand in a vf value intact.
- Updates the list of endpoints and fields that support filtering.
Closes #1200
Closes #1431
Refs #826, #578
Verification
Tested against Tableau Cloud (REST API 3.30) for workbook names and against a Tableau Server running REST API 3.31 for case behavior on users, groups, projects and workbooks. The * wildcard matched at the start, end and middle on Cloud workbook names and on Server project names. The In operator was tested with names containing spaces and an ampersand.
🤖 Generated with Claude Code
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
The filter docs only said ampersands and commas are unsupported, with no
workaround, and did not say which fields support wildcard searches or
the cieq and has operators. Document the asterisk workaround for values
containing & or , (with a client-side exact-match check), the REST API's
like operator and the fields it applies to, and add the missing
CaseInsensitiveEquals and Has operators to the operator lists.
Closes #1200
Co-Authored-By: Claude Code <[email protected]>
The list named four endpoints and seven fields, far fewer than the
library supports. Describe the endpoints by what they accept and point
at RequestOptions.Field for the full set of fields.
Co-Authored-By: Claude Code <[email protected]>
Checked against a Tableau Cloud site (REST API 3.30): an Equals filter
treats * as a wildcard at the start, end and middle of a workbook name,
which makes the documented workaround for values containing & or ,
work, while like, cieq and has are rejected with a 400 on workbook
names. Document this and remove the untested-workaround caveat.
Related to #1200
Co-Authored-By: Claude Code <[email protected]>
Tested against Tableau Cloud: TSC percent-encodes the query string, so
an ampersand in a filter value is accepted. A comma is rejected even
when encoded or preceded by a backslash. The earlier text said both
characters failed.
Co-Authored-By: Claude Code <[email protected]>
Readers of the special-character and wildcard sections could apply them
to vf() export filters, where a comma separates alternatives, a
backslash escapes it, and asterisks are literal.
Co-Authored-By: Claude Code <[email protected]>
Equals on workbook, data source, project and user names, and on workbook
content URLs, ignores case. Equals on a group name is case-sensitive on
Tableau Server.
Refs #1200
Co-Authored-By: Claude Code <[email protected]>
Values can contain &, but only from REST API 3.7 when TSC encodes the
query string. The Value row said & is not allowed.
Co-Authored-By: Claude Code <[email protected]>
Prefix, suffix and middle * matched on workbook names (Tableau Cloud)
and project names (REST API 3.31), ignoring letter case.
Co-Authored-By: Claude Code <[email protected]>
This branch has not been deployed
No deployments
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|