Project Task Planned end date changes on load and causes users not to be able to save intuitively

[kirkr]

When loading an existing Project Task that has had the Planned duration altered by some means, this causes the Planned end date to be changed, you aren't able to close this Project Task in an intuitive manner.

An example is loading a specific PRJTSK, it initially shows such as this

Then this recalculates to the new value

If you change this to Closed Complete immediately afterward, the system will not allow you to close it.

I've tracked this down to the Client Script Check Valid Task Start Date and Set End that changes the Planned end date to be altered. This in turn causes the Business Rule Disable the Change of Planned Dates to prevent the task from being closed and shows the error message.

The work around is that once the Planned end date changes from the Client Script, you must first Save the record and then you may change the status to Closed Complete.

There is a project setting Enable altering of planned date(s) for task in WIP/Closed but this will not resolve this. That not considered within the Business Rule for any closed states.

Is there any proper solution to not need to customize the OOTB code so that users may close their PRJTSK intuitively?

[Inactive_Use167]

Hey,

I have a similar issue, the planned end date before loading shows 03:00:00 PM but after fully loaded the date changes to 03:51:25. I have no clear idea why the system is changing the date after load. As i see the planned end date is calculated from the field below it i.e. Planned duration.  

I am currently checking for the definition of that 1 day in service now

Where you able to find any solution for this issue.?

Thanks

[kirkr]

I haven't found a solution that wouldn't be to alter the OOTB code yet.

As far as I can tell the Planned end date is based on the Planned duration calculated over the Schedule that the Project is operating over.

If you track the code backwards, it gets all the way down to a server API that we don't have access to, SNC.PlannedTaskAPI, so I can't say with absolute certainty what that does.

It seems I'll need to customize the OOTB code to fix this unfortunately.