Help with the output format of lastNote calculation | Community
Skip to main content
J
John_MitchellTek
Employee
September 5, 2023
Solved

Help with the output format of lastNote calculation

  • September 5, 2023
  • 1 reply
  • 547 views

Hi Everyone,


My team was previously using a calc that looked like WEEKDAYDIFF({lastUpdateDate}, $$TODAY) to see when the last time a request/issue/project was updated. 

 

However, as the use of the platform and the complexity of our systems has started to increase, we noticed that this calc was picking up some undesired system updates driven by some added calculations to custom forms (Namely: a set of status timestamp fields coupled with a tracking field to check when a project goes from "Open" to "Closed").

 

Now, I've switched to this calc: 

ROUND(DATEDIFF($$TODAY, {lastNote}.{entryDate}),1)
 
However I'm not entirely sure I like it as I will see if the most recent update is made within the same business day, I actually get a negative number for the day E.g. (-0.5).

Anyone have an idea on how to only show whole positive numbers here? Whether it be here in the custom form calc, or an additional edit to the textmode that displays this column?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Doug_Den_Hoed__AtAppStore

 

Hi @john_mitchelltek,

 

If you've not yet met, may I introduce you to the CLEARTIME calculated data expression, as follows?

 

ROUND(DATEDIFF($$TODAY, CLEARTIME({lastNote}.{entryDate})),1)

 

Regards,

Doug

1 reply

Doug_Den_Hoed__AtAppStore
Doug_Den_Hoed__AtAppStoreAccepted solution
New Participant
September 5, 2023

 

Hi @john_mitchelltek,

 

If you've not yet met, may I introduce you to the CLEARTIME calculated data expression, as follows?

 

ROUND(DATEDIFF($$TODAY, CLEARTIME({lastNote}.{entryDate})),1)

 

Regards,

Doug

    J
    John_MitchellTekAuthor
    Employee
    September 6, 2023

    Hi Doug,

     

    I hadn't though to just wipe the lesser piece of the problem (that we don't actually even need) so thank you for the suggestion!

     

    My mind was in the world of valueformats and jumping calculations. Much easier!

      Terms & ConditionsAccessibility statement

      Loading footer...