You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user filters should support filtering based on email eq and email in.
****Type 3: new functionality****
Requests for totally new functionality will generally be passed to the relevant dev team, but we probably can't give any useful estimate of how or when it might be implemented. If it is a feature that is 'about' the API or programmable access, here might be the best place to suggest it, but generally feature requests will be more visible in the [Tableau Community Ideas](https://community.tableau.com/s/ideas) forum and should go there instead.
Description
A clear and concise description of what the feature request is. If you think that the value of this feature might not be obvious, include information like how often it is needed, amount of work saved, etc. If your feature request is related to a file or server in a specific state, describe the starting state when the feature can be used, and the end state after using it. If it involves modifying files, an example file may be helpful.
Currently the user filter supports searching based on name, luid, friendlyName, and a few other fields. As mentioned in #907:
Note: Filter expressions can’t contain ampersand (&) or comma (,) characters because these characters are used as field expression separators. This is true even if those characters are encoded.
so most servers I have interacted with, friendlyName does not work for searching due to names showing up as "Last, First." Searching by email will offer up a convenient way to find intended users.
The text was updated successfully, but these errors were encountered:
Summary
The user filters should support filtering based on email eq and email in.
Description
A clear and concise description of what the feature request is. If you think that the value of this feature might not be obvious, include information like how often it is needed, amount of work saved, etc. If your feature request is related to a file or server in a specific state, describe the starting state when the feature can be used, and the end state after using it. If it involves modifying files, an example file may be helpful.
![](https://camo.githubusercontent.com/c1f23e24cc21e00f0da3c029d056ea069eacd0e06dfbd2b148a7324bda963e96/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f7761726e696e672d42652532306361726566756c2532306e6f74253230746f253230706f7374253230757365722532306e616d657325324325323070617373776f72647325324325323061757468253230746f6b656e732532306f72253230616e792532306f74686572253230707269766174652532306f7225323073656e736974697665253230696e666f726d6174696f6e2d726564)
Currently the user filter supports searching based on name, luid, friendlyName, and a few other fields. As mentioned in #907:
so most servers I have interacted with,
friendlyName
does not work for searching due to names showing up as "Last, First." Searching by email will offer up a convenient way to find intended users.The text was updated successfully, but these errors were encountered: