C
CS
Hi
We are experiencing problems with Custom Task fields on the My Tasks page.
Scenario:
We create a Custom Task field (which rolls down to Assignment level).
We add the Custom Task Field to Microsofts default My Tasks view as well as
Microsoft's default Assignment Detail view (displayed when you click on the
task name on the My Tasks page).
We create a MSP schedule and add data to the custom task field - and
publish.
On the My Tasks page in PWA the data for the custom task field is displayed
correct.
Editing data in the default view proves to work 100% but the we:
Click on the Task and edit info on the assignment detail view (with the
custom task field and data displayed), we then save and close this view. We
are then automatically pointed back to the default My Tasks view, but now
the custom task field value is gone.
We have been testing this in a couple of environments - we initially thought
that SP1 would solve this, but we have 2 instances with SP1 where this still
happens (and another 2 where it works fine).
Please send me any advise on what could possibly cause this to happen.
Thanks
CJ
We are experiencing problems with Custom Task fields on the My Tasks page.
Scenario:
We create a Custom Task field (which rolls down to Assignment level).
We add the Custom Task Field to Microsofts default My Tasks view as well as
Microsoft's default Assignment Detail view (displayed when you click on the
task name on the My Tasks page).
We create a MSP schedule and add data to the custom task field - and
publish.
On the My Tasks page in PWA the data for the custom task field is displayed
correct.
Editing data in the default view proves to work 100% but the we:
Click on the Task and edit info on the assignment detail view (with the
custom task field and data displayed), we then save and close this view. We
are then automatically pointed back to the default My Tasks view, but now
the custom task field value is gone.
We have been testing this in a couple of environments - we initially thought
that SP1 would solve this, but we have 2 instances with SP1 where this still
happens (and another 2 where it works fine).
Please send me any advise on what could possibly cause this to happen.
Thanks
CJ