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.

Sign up for GitHub

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

Jump to bottom

Add projects as top-level item type in TS Content? #4

Closed
mcoles opened this issue Oct 31, 2019 · 1 comment
Closed

Add projects as top-level item type in TS Content? #4

mcoles opened this issue Oct 31, 2019 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@mcoles
Copy link
Contributor

mcoles commented Oct 31, 2019

Currently TS Content holds a record for every workbook, view, published data source, and flow on Tableau Server. Currently, if you want to know what projects exist and who owns them, you can only see them for non-empty projects. Should we extend this to include a Project item type so that people can answer that question? (note, this is a great use case for the upcoming Data Modeling feature).
@mcoles mcoles added the question Further information is requested label Oct 31, 2019
@mcoles mcoles mentioned this issue Mar 9, 2020
Closed
@mcoles mcoles added help wanted Extra attention is needed enhancement New feature or request and removed question Further information is requested labels Mar 9, 2020
@mcoles
Copy link
Contributor Author

mcoles commented Mar 9, 2020

We've had several requests for this at this point, so I think we'll have to bite the bullet and get it done.

My thought is that we add a new item type of project, such that every project that exists on Tableau gets its own new row in the data source, even if we've already got that information in other rows describing workbooks, or data sources. That would be consistent with the pattern for workbooks and views, where we still show individual workbooks, even if we've already described them somewhat in the records we have for views.

mcoles added a commit that referenced this issue Oct 1, 2021
@mcoles
• All / Multiple:
543be1a 
	Added metadata on Collections (TS Content, TS Events, TS Users) #53
	Added metadata on Metrics (TS Content, TS Events, TS Users, TS Background Tasks) #33
	Incorporate new Web Authoring event into added in 2021.1 (TS Content, TS Events, TS Users) #59
	Updated "Site Role" with improved logic (with thanks to @thechadd) #30
	Version field updated to 03.01

•	TS Events
	Added "details" field #57
	Refactored Historical Item Revision for consistency (should now match revision history from UI) #58

•	TS Content
	Fixed error in "User Filter" calculation #51
	Added projects as top-level item type #4
	Add extract encryption status field #35
	Add "controlled_permissions_enabled" field #19
	Add data_engine_extracts field for Flows #36
	Expanded "access counts" to include a broader set of interactions (web edit, download, export)

•	TS Web Requests
	Fixed incorrect Duration for requests (no longer rounds, and precision increased to milliseconds--thanks to @rk2511) #56

•	TS Background Tasks
	Improved Data Alerts information and added several fields, populated hyperlinks #39
	Added field "Increment Date" that should be used for incremental refreshes, with field "Is Max Record" added as a data source filter.
	Added job creator information #24
	Account for "Cancelled" tasks #32
	Identifying suspended extract refresh failures #41
	Fixed Item Owner info for subscriptions #48
@mcoles mcoles mentioned this issue Oct 1, 2021
Merged
@mcoles mcoles closed this as completed Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mcoles