Skip to main content
Question

How to clean Planned Start and Planned Finish in a Task?

  • March 4, 2026
  • 1 reply
  • 17 views

Forum|alt.badge.img+2


We have created thousands of request with given PlannedStart and PlannedFinish.

Via API-Call we want to clear these both fields and set the other fields

json = $"{{\n";                                                                     
json += $" \"PlannedStart\" : \"\" , ";
json += $" \"PlannedFinish\" : \"\" , ";
json += $" \"EarliestStart\" : \"{EarliestStart}\" , ";
json += $" \"LatestStart\" : \"{LatestStart}\" , ";
json += $" \"LatestFinish\" : \"{LatestFinish}\" , ";
json += $" \"Duration\" : {Duration} , ";
json += $" \"Objsite\" : \"{Objsite}\" ";
json += $"\n}}";

endpoint = $"main/ifsapplications/projection/v1/WorkTaskServiceHandling.svc/JtTaskSet(TaskSeq={TaskSeq})";

response = await Rest.PATCH(endpoint!, json, "", eTagTask);

 

The response throws an error, because PlannedStart and PlannedFinish are not set.

Example:

In the above example: 

Set earliestStart to 11:00, LatestStart to 15:00, LatestFinish to 17:00 on the same day. 

The goal behind is: make the requests (tasks) more flexible by defining a time range.

Our experience is, that PSO only considers PlannedStart and PlannedFinish for optimization when these entries are set.

To raise flexibility we want to kick them out and only set the other time entries.

Any Idea how to solve this?

Best regards

Michael

1 reply

Alexander Heinze
Ultimate Hero (Employee)
Forum|alt.badge.img+25

You mention Request Tasks, but use the WorkTaskServiceHandling, which can already cause issues. Regardless of whether you use Work Order or Requests, I would recommend the “integration” APIs. 

WorkTaskServicesV2 for Work Order Tasks or ReqWorkTaskServices for Request Tasks

Can you try to use ReqWorkTaskServices to do the update?

 

For PSO Planned Start and Planned Finish are not relevant, these attributes are not sent (only Fixed Start will have an effect). If you want to provide a time range that PSO can use to allocate work, use the SLA instead.