From a project level form I need the date a request is created to use in my wait time calculated field. I see others have used convertedOpTaskEntryDate but isn't this the date a request is converted into a project not the date the request was created? I'ved looked in the API Explorer and it shows entry date for issue but can't get the syntax right.
Thanks in advance!!
Solved! Go to Solution.
Views
Replies
Total Likes
@FrankatMSC Based on what you shared above, I created a project custom form and added two different calculated fields:
1. Converted Issue Entry Date (convertedOpTaskEntryDate)
2. # of Days Between Issue Entry Date and Project Actual Start Date, using your calculation from above
I then added this custom form to a project and it's working as expected, so I'm not totally sure why Customer Support mentioned you couldn't use convertedOpTaskEntryDate in a calculated field, because it works.. I even added a third column to the project report with text mode for convertedOpTask:entryDate to make sure it was correct.
With that being said, your calculation is correct for how to capture wait time. If you wanted to calculate the number of days between the date in which a request was converted to a project and the actual completion date of the project, you would swap out convertedOpTaskEntryDate with entryDate since this form is already associated with projects.
Calculated Field = IF(ISBLANK({programID}),ROUND(DATEDIFF({actualStartDate},{entryDate}),0),ROUND(DATEDIFF({actualStartDate},{entryDate}),0))
Hope that helps to clarify things!
Views
Replies
Total Likes
@FrankatMSC The field for convertedOpTask:entryDate would refer to the date in which the request was entered into Workfront, so you should be able to use that in your calculated field. If you want to share your calculation, since you mentioned it's not working, I can try and help!
Views
Replies
Total Likes
@NicholeVargas Thanks for responding. This is the formula I've been using and it works fine.
"Thank you, Frank! Looking into this, I've found that "convertedOpTask" is a dynamic table and cannot be used in a calculated field. However, you can work around this by creating an issue-level field that references the entry date and then pulling that into your project-level calculated field.
Let us know if you have any questions!"
So now it looks like my formulas is correct for how we now want to calculate wait time? IE starting from the date a request is created. What would be the variasble to capture the date a Request is converted into a project then?
Views
Replies
Total Likes
@FrankatMSC Based on what you shared above, I created a project custom form and added two different calculated fields:
1. Converted Issue Entry Date (convertedOpTaskEntryDate)
2. # of Days Between Issue Entry Date and Project Actual Start Date, using your calculation from above
I then added this custom form to a project and it's working as expected, so I'm not totally sure why Customer Support mentioned you couldn't use convertedOpTaskEntryDate in a calculated field, because it works.. I even added a third column to the project report with text mode for convertedOpTask:entryDate to make sure it was correct.
With that being said, your calculation is correct for how to capture wait time. If you wanted to calculate the number of days between the date in which a request was converted to a project and the actual completion date of the project, you would swap out convertedOpTaskEntryDate with entryDate since this form is already associated with projects.
Calculated Field = IF(ISBLANK({programID}),ROUND(DATEDIFF({actualStartDate},{entryDate}),0),ROUND(DATEDIFF({actualStartDate},{entryDate}),0))
Hope that helps to clarify things!
Views
Replies
Total Likes
Thank you Nichole!! Have a great Memorial Day Weekend.
Views
Likes
Replies