Definite solution for "today" handling in calculated fields (days since, days until, countdown,...) / incl. possible solution

Comments

32 comments

  • Official comment
    Andreas Garnæs

    Hi all,

    I don't have an official solution for you, but I want to make a comment about the reasoning behind the current limitations.

    You could argue that calculation fields behave a little counter-intuitively when it comes to using "current time", but there's a good reason for this. It's a little tricky to explain, but bear with me. They key point is that calculation fields are only updated when the data they depend on change. As an example, the calculation x + y will be updated every time x or y changes. Now consider the calculation Current hour + x. The intent of this calculation is to show 9 + x when the time is between 9:00 and 9:59, 10 + x when the time is between 10:00 and 10:59, etc. The problem is that the calculation will only be updated when x changes. If x does not change, then the calculation field will show whatever the hour was when x last changed + x.
    The reason we have to do this is to avoid updating calculation fields all the time. The above calculation would need to be updated every hour, but we could just as well have a calculation Current second + x, which needed to be updated every second! Keeping such calculations up to date would require an enormous amount of computing resources.

    We're working on coming up with a solution that balances flexibility and cost. In the meantime, my best suggestion is to use the API or to set up a "Current time"-app as alluded to in the question.

    Best,
    Andreas

    Comment actions Permalink
  • Stefan Ukena

    I second that. Would love to see this as a feature!

    0
    Comment actions Permalink
  • Rainer Grabowski

    I second that too, Want to get rid of all these "dirty" workarounds for calculating with current dates

    1
    Comment actions Permalink
  • Ron van der Plas

    +1

    0
    Comment actions Permalink
  • Andrew Bridges

    +1, this is a critical oversite

    0
    Comment actions Permalink
  • Heather Fox

    Yes, please.

    0
    Comment actions Permalink
  • nealpatil

    I am planning to implement workaround for Countdown and date/date-time arithmetic etc.
    Please let me know whoever is interested and I will invite to the workspace.
    Contact me at NealPatilATgmx.com (replace AT with @).

    Thanks

    0
    Comment actions Permalink
  • Robin Rist Kildal

    +1 , we could absolutely use this.

    0
    Comment actions Permalink
  • nealpatil

    First try for workaround is completed.
    Data entry of either one date or two dates is expected - which will create external link to calculate Since and Countdown and results like the following will be delivered by clicking external link.

    (1)
    Welcome
    Number of days since 01012015 till 12312015 = 364 days
    Countdown to 01012015 from 12312015 = -364 days

    (2)
    Welcome
    Number of days since 12312015 = -169 days
    Countdown to 12312015 from today = 169 days

    0
    Comment actions Permalink
  • Andreas Forstinger

    Hi @nealpatil,
    good to hear your workaround makes progress.
    But really I would want an official way to handle this kind of scenarios. Solutions via scripts or extensions really should not be necessary for such a simple thing.

    0
    Comment actions Permalink
  • Marco Polo de Jesús Cetina Abreu

    +1 I really want it, all my life would be easier if I had @currentdate

    0
    Comment actions Permalink
  • Sara Høeg Højlund-Rasmussen

    Thanks for sharing your votes and idea :)

    //Sara - Podio

    0
    Comment actions Permalink
  • Rainer Grabowski

    Andreas, thanks for your great explanation. I think, most wanted feature is "current date", not so much "current hour". And most people would be glad to have a token "current date" - which wouldn't need so much computer resources as your example with hours and which could be updated over 24 hours due to the timezones. A token like "@created on" on which you can use moment() to then get current week, current month, current year.
    We solve this with Globiflow and also with a "current day App" (with one item which has one date field only). But all these workarounds are cumbersome ( "dirty" as I mentioned in another comment here). Especially the "current day App", which has to be related to every item in each app which needs to deal with current day cause Podio Advanced Flow don't allow to relate a new item automatically to a specific item (Btw: Why not?")

    Cheers,
    Rainer

    2
    Comment actions Permalink
  • Hamid

    +1 for this

    0
    Comment actions Permalink
  • Simon Midtgaard Guldberg

    +1 need it

    0
    Comment actions Permalink
  • Mitchell Ogden

    +1

    0
    Comment actions Permalink
  • Daniel Martins

    +1 need it

    0
    Comment actions Permalink
  • Matt Clifton

    Adding my vote too - need this! :)

    0
    Comment actions Permalink
  • Matthew Rideout

    Thanks Andreas for the answer. Any response to not needing 'Current second' but mostly day?. Or how likely this is to become a reality? I have many clients who would benefit from seeing day counting (related to current date). Thank you

    0
    Comment actions Permalink
  • Gus H.

    .....I bet Rainer has a solution....Luv 2 hear from you man :-).

    0
    Comment actions Permalink
  • Rainer Grabowski

    Indeed I use a workaround. It's a current time app. All my clients can count days and in some way hours (related to current date/time). With the right app design you can use it in many apps across workspaces. And it helps for creating live reports.

    Rainer
    rg@delos-consulting.com

    0
    Comment actions Permalink
  • Veerle Pinxten

    Hi Rainer, thank you for exploring. Am I right that you have a current time app? Do you wanna share? It would be helpful for many of us. Or where can I find it? Kind regards, Veerle

    0
    Comment actions Permalink
  • Rainer Grabowski

    Hello Veerle

    the Current Date App has only one Item with 2 fields: A title field and a date field (you even don't need the title field). This date field is updated every day to the the current date. You can do that manually or (more comfortable and more reliable) automatically by a flow with Globiflow. 

    The trick is to have access to this current date item in every app where you need it. To have access means: You need a relationship to this item. The relationship can be direct or indirect. Direct means: In App A you have a relationship field which points to the Current Date app. Indirect means: App A has this relationship and App B is related to A, but not to Current Date. But with the right app design, App B can get the current date through App A. 

    One example how I often build these relations for my customers:
    First I create the Current Date App (CD), with an item which has the title "Central Timer" and a date field "Today's Date".
    Then I look for an app which is related to many other apps. That's often an employee app (with an item for each employee) or a contact app (cause these apps are often related to Projects, Deliverables etc. ), but it can be every other app.

    In this Central App (CA) I add a relationship field "CD Relation" to CD. Then I export the existing CA- items. In the sheet I enter in each cell in the empty column the title of the CD-item "Central Timer" and re-import the sheet. Now every CA-item is related to the CD-item. If you make the field CD-Relation a required field you won't forget to link new CA-items to CD (can also be done by Globiflow automatically). 

    Next step: In CA I add a calculation field "Today" and enter: @Max of Today's Date (this gets the date from CD). Click done, now you have the daily updated current date in each CA-item. And in each app which is related to CD you now can grab the current date from the field  "Today" and use it in the calculation fields in the other apps. 

    HTH,
    Rainer

    0
    Comment actions Permalink
  • Veerle Pinxten

    Thank you Rainer! Your explanation was very clear and it works. May I ask something else? I want to program a calculation:

    If @variabele is divisible by 365 (round number), then I want the text "it's time for a conversation with staf". Is this possible? I have to learn a lot! Thank you very much. Kind regards, Veerle

    0
    Comment actions Permalink
  • Rainer Grabowski

    That's 

    @variable % 365 == 0 ? "it's time for a conversation with staf" : "";

    One tip: For such calculation questions there's an own forum https://help.podio.com/hc/communities/public/topics/200101427-6-Calculations

    Rainer

    0
    Comment actions Permalink
  • Veerle Pinxten

    Thank you very much, Rainer!

    0
    Comment actions Permalink
  • Alexander Mouschovias

    Reviving this thread again, has there been any movement on an official solution without these dirty workarounds? Updating date-based calculations daily really shouldn't add that much server load, and as you can see from the comments there's a lot of demand for this!

    2
    Comment actions Permalink
  • David Gélinas

    When I try to grad the Today value from the Central app, it's always returning yesterday at 7pm...

    0
    Comment actions Permalink
  • Luca Sorgiacomo

    Second that. So important to automatically update date/time based calculations without hacky workarounds. To save resources could you not shift part of the updating logic to the browser? I can't believe you have to rely only on server-side updates...

    0
    Comment actions Permalink
  • Christoph Speckmann

    Hey Andreas,

    just in case this would interesting for evaluation: I would pay for that feature to compensate your additional required resources. I also have to do that for other tools in online marketing when it comes to tracking e.g. Supermetrics. Just from my perspective I wouldn't have any problem to pay for that.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk