0

I would like to set values to plannedCompletionDate and projectedCompletionDate. I understand they are calculated fields from answer. My requirement is to update these fields with respect to a project. My code is as below 

  `https://{exz}.attasksandbox.com/attask/api/v5.0/project/57cd--eaf1b824d3?projectedCompletionDate=1990-01-01&taskConstraint=MSO&apiKey=8ud---ky8j&method=put`

I also tried 

`https://{exz}.attasksandbox.com/attask/api/v5.0/project?ID=57cd--eaf1b824d3&projectedCompletionDate=1990-01-01&taskConstraint=MSO&apiKey=8ud---ky8j&method=put`

But I get error as

"APIModel V5_0 does not support field taskConstraint (Project)"

I also tried replacing taskConstraint with projectConstraint, but end up in similar error. What constraint should I override to set values to projectedCompletionDate and plannedCompletionDate? Note -These are project properties and not task. Thanks in advance!

Community
  • 1
  • 1
Paalya
  • 9
  • 5

1 Answers1

0

You can't set the projected dates at all, but you can manipulate the timeline engine to set them for you. Do do this through the planned dates, constraint type, constraint date, completion mode, and percent complete.

It should be noted that you can't set anything on the project level but the one planned date that corresponds to the schedule mode of the project. Your calls are at the project level and therefore will not work. The project calculated planned and projected dates are rolled up from the tasks. You would need to set them there and then allow the rollups to happen.

May I ask the business case and reason you need to manipulate these dates? We maybe able to find another solution that would be more straight forward.

jclawton
  • 241
  • 1
  • 2
  • jclawton: Thanks for your reply. My requirement is to set these fields blank. I basically want to tell workfront engine not to compute any values for these fields – Paalya Sep 08 '16 at 01:45
  • Sorry that is not going to happen. These values are always calculated and cannot be null. Even personal tasks have values in these fields. What is the business case for having these fields to be blank and I might be able to help with a different solution? – jclawton Sep 09 '16 at 16:40
  • jclawton: Thanks for enlightening me on this. My BA is happy to keep it untouched. But, I would need to update other hidden project property fields such as CategoryID, CompanyID, ResourcePoolID and others. I shall post question in another thread, if I am unable to achieve it. Thanks again! – Paalya Sep 12 '16 at 05:54
  • jclawton: I have posted my another question [here](http://stackoverflow.com/questions/39461984/attask-update-hidden-project-properties-through-api) – Paalya Sep 13 '16 at 04:00