Forum Discussion
- DavidHaweQrew TraineeThere may be better solutions but I would do it like this:
Two fields for the end date. "End Date" which is a formula-date field and the field you use in reports and duration calculations and "Input End Date" to input the date when you have an actual end date.
The formula for "End Date"
If(IsNull([Input End Date]),Today(),[Input End Date])- NenadIlicQrew Assistant CaptainThis is a good option, but the idea behind is:
* I have start date and end date, but I don't know when the end date will be (in case of delays)
* so my duration counter is working based on delays as each day passes I can see that delay duration is prolonging, and that it is not affecting project aging (due to delay that was encountered).
If I use two fields, I might not be able to track it properly.
I was also thinking if there is a possibility of using yuor formula-date field, in combination with checkbox field, so when the checkbox is checked, the delay is closed.....
somehow to combine:
If [checkbox] is unchecked, If(IsNull([Input End Date]),Today(),[Input End Date])
If [checkbox] is checked, enterdate
Do you think this solution might be achievable?
- KingslySamuel1Qrew Assistant CaptainWill it help if you use the native solution of selecting "default date" to "today" on the "field settings" - just wondering!
- DavidHaweQrew TraineeThe formula field is native. Also the default setting set the value when the record is created but does not remain the current date when the record is opened on future dates
- NenadIlicQrew Assistant CaptainYup, I thought that the formula will autoupdate the field for today, but realized that it is only for the date of creation.