-
1. Re: data update time for published data source
Donna Coles
Jun 5, 2018 6:23 AM
(in response to lingyou syu)
Hi there
Can you advise what version of Tableau Server you are using or whether you're using Tableau Online. I can't see the 'Data Update Time' displayed when I view the details of an extracted data source on my server (but it is v10.1).
Thanks
Donna
-
2. Re: data update time for published data source
Jeff Strauss
Jun 5, 2018 7:48 AM
(in response to lingyou syu)
Is your "orange" data update time a custom field within your dashboard or where does it surface? Maybe is this the max time within your data?
-
3. Re: data update time for published data source
Maria Tishkova Jun 6, 2018 1:00 AM (in response to lingyou syu)I have the same problem.
Worked as intended in 10.3 on server and desktop, the Data Update timestamp displayed the extract time (even though the connection from the workbook to the extract on server was "live"), but after the update to 2018.1 (both desktop and server) the timestamp displays the current time, i.e. the time of that one live connection to the extract. I'm not sure if it's a bug or a feature though.
Any idea how to display extract time in the workbook that is connected "live" to that extract?
-
4. Re: data update time for published data source
lingyou syu Jun 6, 2018 2:21 AM (in response to Donna Coles)My Tableau Server version is 10.5.
-
5. Re: data update time for published data source
lingyou syu Jun 6, 2018 2:21 AM (in response to Jeff Strauss)data update time is Tableau's formal field, not my custom field.
You can add it by following this post: Adding Data Refresh Time Stamp to a View in a Dashboard | Tableau Software
-
6. Re: data update time for published data source
Donna Coles
Jun 6, 2018 3:20 AM
(in response to lingyou syu)
Ok, based on the link you sent, the data you're showing is presented in a workbook you've built and not part of any of the standard server screens.
Given the article states that it should show the date of the last extract, and the article was recently updated (May 2018), and another user is suggesting they have seen a change in behaviour too, I would be raising this to Tableau Support as a possible bug. I can't see anything relating to this on here Known Issues | Tableau Software
Donna
-
7. Re: data update time for published data source
Maria Tishkova Jun 14, 2018 3:25 AM (in response to lingyou syu)1 of 1 people found this helpfulI contacted Support regarding this issue, and it's not a bug but a feature. Seems like a server/desktop update, since Data Update time stamp displayed the extract time before, and now it displays the time of "live" connection between the workbook and the extracted data source. The Support technician has logged a feature request on my behalf "for the Product Management team to review for possible support in a future release". They also confirmed that there's no workaround for a data source extract time stamp. I've deleted this time stamp from my workbooks, so my users and I just have to wait for a new feature.
-
8. Re: data update time for published data source
Toby Erkson
Sep 24, 2018 11:29 AM
(in response to Maria Tishkova)
Can you please post the URL to the Idea so it's easier for others to find and vote up.
-
9. Re: data update time for published data source
Toby Erkson
Oct 9, 2018 2:01 PM
(in response to Toby Erkson)
1 of 1 people found this helpfulTook matters into my own hands: https://community.tableau.com/ideas/9303
-
10. Re: data update time for published data source
Jonathan Brough Jun 17, 2019 5:17 AM (in response to Maria Tishkova)HI,
I was also getting this issue, on a published workbook that connects to a data source which is scheduled to extract from Excel once a week.
The 'Date Update Time' Tableau function, added using the Insert options on a 'Edit Title' dialogue, was returning the datetimestamp of the user accessing the page.
I had another workbook that was not getting this problem, and the difference appears to have been that this other workbook had a filter set on the 'Edit Data Source' screen (top right). Setting one up seems to have resolved my problem.
Thanks,
Jonathan
