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

TS Content: Refactor Revision / Content Version fields for consistency #64

Open
mcoles opened this issue Nov 8, 2021 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@mcoles
Copy link
Contributor

mcoles commented Nov 8, 2021

Same as #58 but for TS Content. Why didn't just we do this in 03.01? Didn't think to. :(

@mcoles mcoles added the enhancement New feature or request label Nov 8, 2021
@mcoles mcoles changed the title TS Content: Refactor Historical Item Revision for consistency TS Content: Refactor Revision / Content Version fields for consistency Nov 8, 2021
@DigitalDuquette
Copy link

I'm trying to find some documentation here to explain why the revision numbers in this data source (ex. 41.5) don't match the whole number integer shown in Tableau Server (ex 140).

https://help.tableau.com/current/pro/desktop/en-us/qs_revision_history.htm

Revision history in Tableau documentation references the whole number, but these data sources provide values that I can't tie out in the server GUI. I have to be searching for the wrong key words here.

@mcoles
Copy link
Contributor Author

mcoles commented Aug 28, 2023

If you look at #58 I refactored the TS Events data source to reconcile what's in PostgreSQL with what you'd see in the UI. I forgot to add that logic to TS Content as well, which is why it's different. You could grab the calc from TS Events and likely re-apply it to TS Content as well. As for why we store it differently in PostgreSQL, I have no idea :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants