-
Notifications
You must be signed in to change notification settings - Fork 436
Some revision properties not populating #1175
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
Comments
https://github.com/tableau/server-client-python/blob/master/tableauserverclient/models/revision_item.py#L70-L72 Actual xml response for my real revision example above: <?xml version=\'1.0\' encoding=\'utf8\'?>\n<ns0:revision xmlns:ns0="http://tableau.com/api" revisionNumber="44" publishedAt="2021-10-28T16:11:34Z" deleted="false" current="true" sizeInBytes="128582">
Not sure if this should be fixed in TSC or in the Tableau REST API itself because the expected values appear to match the Tableau REST API naming conventions more closely. CC @jorwoods since we are chatting about this is Slack right now |
Thanks @jharris126! The official documentation does not match what is actually returned by the server endpoint. https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_revisions.htm#get_workbook_revisions |
https://github.com/tableau/server-client-python/blob/master/tableauserverclient/models/revision_item.py#L73 |
I'm having this same issue. Got a ton of "Nones" when trying to populate the same fields you're talking about. |
When can we expect the fix for this to be published? I'm running into the same issue. |
fix is merged - should be published this week. |
Thank you! Looking forward to it! |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Key revision properties (
current
andcreated_at
) of theRevisionItem
are not populating or populating with default values.Versions
Details of your environment, including:
To Reproduce
Results
revision_number
andcurrent
properties of theRevisionItem
object are populating with default values instead of correct values.The text was updated successfully, but these errors were encountered: