Closed Subhash-Daggubati closed 3 years ago
Hi @Subhash-Daggubati if a parameter that does not map to any functionality is passed then there will be no impact on Tableau's side. In your example, you would want to be specifying fields=_all_
.
You would need to define your parameter dict in this case as {"<your_chosen_param_label>": "fields=_all_"}
.
At the surface it seems that the "fields" should just be the key of the dict, and then the value you are setting for "fields" should be the value in the key/value pair, but this does not generalize to other values that can be specified to append to URL requests. The existing parameter_dict
configuration generalizes to specifying filters ("vf_
You could argue that the above issue could be handled by making filter keys follow the "vf_
There is no difference in the response for the following lines of code.
conn.get_users_on_site() conn.get_users_on_site(parameter_dict={'fields':'all'})
Based on Tableau REST API documentation, when the fields parameter with value all is passed, the response should also have email and Full Name details. But it is returning the default response.
https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_fields.htm#get-users_site