Explore recipe: Creating a last refresh timestamp

Return to top
Have more questions? Submit a request

11 Comments

  • Ron de Vries

    Hi Rob,

    Doesn't the below already show the last update of the dataset? Or am I missing something?

    Next to that it would be nice if the '' Last update timestamp'' shows on the datasets page by default.

     

    Regards,

    Ron

    0
  • Rob Stack
    Zendesk Documentation Team

    Hi Ron de Vries you are indeed correct. Since this recipe was released, the functionality has been included in the product. I'm leaving this recipe up though as it's a good tutorial on date management.

    Your suggestion about the last update time stamp would be a great one to add to our product feedback page at https://support.zendesk.com/hc/en-us/community/topics/360001200913

     

    0
  • Spencer Hutton

    Where in the product can we use this functionality?  I have created the query per the recipe (great tip), but if it is built in, where is it?

    0
  • Rob Stack
    Zendesk Documentation Team

    Hi Spencer, thanks for the question. You can now see it at the top left corner of any query.

    I hope this helps!

    0
  • Spencer Hutton

    Thanks Rob, and thanks for all of your articles, I have read and learned a bunch.

    I do see that Last updated, but I really wanted to put something on a dashboard visible to the users.  I guess that means that this recipe is what is needed for that.

    0
  • Rob Stack
    Zendesk Documentation Team

    Thanks Spencer Hutton I'm really glad the articles help!

    Yes, I think for now anyway, this recipe is a great way to get that information onto a dashboard. Have a great weekend!

    0
  • CJ Johnson

    It looks like this unfortunately doesn't work anymore. It says this queries too many rows, and snips the data, so the timestamp is shows is way off (like, it showed me a timestamp with the year 2013). 


    Edit: The easy fix: For most folks, add in a "Ticket Updated - Date" filter set for "Today". You might get weird results for midnight runs, or if your data updates daily instead of hourly, but otherwise should avoid data overload and getting a wildly wrong date. 

    0
  • Kate L.

    Hi CJ,

    Apologies for the delay here. I have created a ticket on your behalf so we can look into your query further.

    0
  • Brandon Niblock

    It does appear to no longer work. Even with the steps CJ added its still off.  Right now the data set is 34 minutes last update, this formula is showing 86 minutes.

    0
  • Darenne Carbajosa

    Hi Brandon, 

    Apologies for the delayed response. In order for us to properly investigate this, I've created a ticket on your behalf to look into this further. 

    0
  • Erin O'Callaghan
    Zendesk Documentation Team

    Hi all, I just wanted to post a quick note to clarify how this recipe works, in light of a few of the comments above:

    • The built-in dataset sync timestamp in the upper left of the query builder measures the last time Explore's behind-the-scenes process ran to update data, regardless of whether there was actually new data to be updated.
    • The timestamp created by this recipe, on the other hand, measures the last time a ticket was updated as long as the update happened before the last dataset sync. (Otherwise Explore wouldn't know about that ticket update because the sync hasn't run yet.)

    So while this recipe isn't an exact replacement for the dataset sync timestamp, it's still a useful way for dashboard viewers to know approximately how current the info on a dashboard is. Hope that helps! 

    0

Please sign in to leave a comment.

Powered by Zendesk