Duration Date/Time and Dates
I am trying to figure out a formula for duration. my problem is that one set of date is Date/Time, while the other is only Date.
QC Date - Date/Time Start Date - Date The QC Date pulls from a r...
Forum Discussion
This will give you a Duration result
ToDate([QC DATE CREATED])-[DESIGN START DATE])
Personally I find duration fields confusing to work with. I prefer to have a numeric field representing the # of days when dealing with short term time ranges.
This would be a numeric field​
ToDays(ToDate([QC DATE CREATED])-[DESIGN START DATE]))
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
ToDate([QC DATE CREATED])-[DESIGN START DATE])
Personally I find duration fields confusing to work with. I prefer to have a numeric field representing the # of days when dealing with short term time ranges.
This would be a numeric field​
ToDays(ToDate([QC DATE CREATED])-[DESIGN START DATE]))
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
- I agree with Mark as this can keep the units consistent as well, although, displaying smart units can be nice too depending on the use case and actual time windows.
Often times we'll store data in a datetime field so it's available if we need more granular timeframes, but have "helper formula fields" to cast the datetime to a date. This can reduce keeps noise on reports by omitting timestamps when necessary and can make your formulas a bit easier to read.
For example, the field "Start Timestamp" and a helper "Start Timestamp To Date" that is:
ToDate([Start Timestamp]). Then, use consistent field types in your duration calculations.
[QC Timestamp To Date] - [Start Timestamp To Date]
And as Mark pointed out you could represent these Durations as Numeric Days instead using ToDays() and changing the formula field type to numeric.
------------------------------
Brian
------------------------------
