Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a way to query for specific views based on content_url #456

Closed
mcoles opened this issue Jul 2, 2019 · 3 comments
Closed

Need a way to query for specific views based on content_url #456

mcoles opened this issue Jul 2, 2019 · 3 comments

Comments

@mcoles
Copy link

mcoles commented Jul 2, 2019

Currently the REST API requires you to provide the ID value or user-friendly name for a view if you wish to retrieve information about a specific one. However, I need a way to search for a view based on a content_url. This provides a human-readable method to reference a unique viz on a given site. Not having it means that I have to pull the full list of views from the entire site, then lookup the ID value based on the content_url. This takes at least thirty seconds, which isn't unfortunately isn't acceptable for my application.

Could we please add content_url to the list of filterable fields? I realize this is a request for the REST API, but I'm adding it here because I assume it will take work to be implemented in the TSC wrapper as well, and I'd love to keep my work in "pure" TSC as much as possible.

thank you,
Matt

@jacalata
Copy link
Contributor

This was added in the REST API version 3.6. We can add it to the next version of tsc, but you can also use the plain string as the field name for now:
options.filter.add(TSC.Filter('contentUrl',
TSC.RequestOptions.Operator.Equals,
"Regional"))

@jacalata jacalata added the in-progress Issues that are in-progress of being fixed label Oct 26, 2021
@mcoles
Copy link
Author

mcoles commented Oct 26, 2021

Thank you for letting me know!

jacalata added a commit that referenced this issue Apr 12, 2023
jacalata added a commit that referenced this issue Apr 13, 2023
jacalata added a commit that referenced this issue Apr 19, 2023
jacalata added a commit that referenced this issue Apr 24, 2023
TableauIDWithMFA added to the user_item model to allow creating users on Tableau Cloud with MFA enabled (#1217)
Run long requests on second thread (#1212)
#1210
#1087
#1058
#456
#1209
update datasource to use bridge (#1224)


Co-authored-by: Tim Payne <[email protected]>
jacalata added a commit that referenced this issue Sep 22, 2023
* fix: TableauIDWithMFA added to the user_item model to allow creating users on Tableau Cloud with MFA enabled (#1216)
* fix: make project optional in datasources #1210
* fix: allow setting timeout on workbook endpoint #1087
* fix: can't certify datasource on publish #1058 
* fix filter in operator spaces bug (#1259)
* fix: remove logging configuration from TSC (#1248)
* Hotfix schedule_item.py for issue 1237 (#1239), Remove duplicate assignments to fields (#1244)
* Fix shared attribute for custom views (#1280)

New functionality
* enable filtering for Excel downloads #1209, #1281
* query view by content url #456  
* update datasource to use bridge (#1224)
* Add JWTAuth, add repr using qualname
* Add publish samples attribute (#1264)
* add support for custom schedules in TOL (#1273)
* Enable asJob for group update (#1276)


Co-authored-by: Tim Payne <[email protected]>
Co-authored-by: Lars Breddemann <[email protected]>
Co-authored-by: jorwoods <[email protected]>
Co-authored-by: Austin <[email protected]>
Co-authored-by: Yasuhisa Yoshida <[email protected]>
Co-authored-by: Brian Cantoni <[email protected]>
Co-authored-by: a-torres-2 <[email protected]>
Co-authored-by: Łukasz Włodarczyk <[email protected]>
@jacalata jacalata closed this as completed Jan 9, 2025
@jacalata jacalata added done and removed in-progress Issues that are in-progress of being fixed labels Jan 9, 2025
@mcoles
Copy link
Author

mcoles commented Jan 9, 2025

Thank you, @jacalata! 👍

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

No branches or pull requests

3 participants