A
akmckain
We have custom developed an Outlook add-in which updates timephased
task and timesheet data simultaneously. We have only just implemented
this in live production and are finding that in some schedules, the
actuals do not update into the schedule correctly even though the
Applied Task Update Requests which are accessed through the Task
Approvals page on PWA always shows the data correctly. A number of
very strange things are happening including: actuals being recorded
against extended periods of time (eg 30 years), actuals being recorded
on the wrong days, actuals in addition to that which was approved
being recorded (eg on the start date of the task), actuals not being
recorded (in this case there is a X on the Applied Task Update
Requests and Errors page in the information column which states that
there was an internal error applying the update).
Has anyone else experienced anything similiar? We have had to
completely re-create one of these schedules to try and resolve the
issue but we have at least three schedules this has happened to and
are concerned that this could continue.
task and timesheet data simultaneously. We have only just implemented
this in live production and are finding that in some schedules, the
actuals do not update into the schedule correctly even though the
Applied Task Update Requests which are accessed through the Task
Approvals page on PWA always shows the data correctly. A number of
very strange things are happening including: actuals being recorded
against extended periods of time (eg 30 years), actuals being recorded
on the wrong days, actuals in addition to that which was approved
being recorded (eg on the start date of the task), actuals not being
recorded (in this case there is a X on the Applied Task Update
Requests and Errors page in the information column which states that
there was an internal error applying the update).
Has anyone else experienced anything similiar? We have had to
completely re-create one of these schedules to try and resolve the
issue but we have at least three schedules this has happened to and
are concerned that this could continue.