Repository navigation
Document filter special characters and the wildcard workaround - #1906
Merged
Merged
Conversation
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 <noreply@anthropic.com>
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 <noreply@anthropic.com>
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 <noreply@anthropic.com>
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 <noreply@anthropic.com>
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 <noreply@anthropic.com>
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 <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
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 <noreply@anthropic.com>
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 <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Remove the operator and field scope claims, the case-sensitivity paragraph, the like operator table, the view filter section, the In list section and the version-specific encoding and wildcard claims. Keep the comma failure, the asterisk workaround, and the Has and CaseInsensitiveEquals operator rows. Co-Authored-By: Claude Code <noreply@anthropic.com>
jacalata
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
*workaround with a client-side check.&in a name is matched as written.HasandCaseInsensitiveEqualsto the operator lists and the operator table, with aname__cieqexample.*matches any run of characters in a filter value.Closes #1200
Refs #1431
Verification
Tested against Tableau Cloud (REST API 3.30) for workbook names: the comma error, the
*wildcard and the&match.🤖 Generated with Claude Code