D
Denis in Brisbane
I want to use customised resource fields that are local to individual
projects. However, when the project is opened they get overwritten (set to
zero) as the resource is downloaded from the server. This is true even for
custom fields such as Cost 1 - not just enterprise fields like Enterprise
Cost1.
I know standard fields get overwritten but I was expecting non-Enterprise
fields to be left alone.
I'm still struggling with having a different rate for the same resource on
different projects (more than 5 and easier than using rate tables).
I know that when I open a project the resources' Standard Rates get
downloaded from the server. I thought maybe I could use Cost 1 as a local
resource rate and set it to different values in different projectsand then
have an auto_open macro that overwrites StandardRate with local rate.
Unfortunately Cost1 gets set to zero when the project is reopened (I know
it's going to be because when I type something in it I get a warning message
- and it's not kidding!) . Bummer.
It actually seems to me to be a bug rather than a feature.
Related issue. When I do what I tried and save the project, it shows in the
Projects list with a cost based on my local rate. When I publish it, the
Project Center views show it with the 'local' cost but when I drill down into
the Project views it shows with cost based on the Standard Rate. This
implies that project server (or maybe Project Pro) is recalculating the task
level costs at the time the tasks are published or Project Server is doing it
at the time the Project view is generated. I thought Project Server just
stored the data it had been passed from Project Pro. Whatever - it means
that even if I could get the 'local rate' to work the way I want Project
Server would show a contradiction between what's visible at the Project views
from what's shown at Project Center. Another bummer.
I'd be interested in other opinions and particularly interested if you've
found a way to handle the different rates problem. It's likely to be a
show-stopper for us.
Denis
projects. However, when the project is opened they get overwritten (set to
zero) as the resource is downloaded from the server. This is true even for
custom fields such as Cost 1 - not just enterprise fields like Enterprise
Cost1.
I know standard fields get overwritten but I was expecting non-Enterprise
fields to be left alone.
I'm still struggling with having a different rate for the same resource on
different projects (more than 5 and easier than using rate tables).
I know that when I open a project the resources' Standard Rates get
downloaded from the server. I thought maybe I could use Cost 1 as a local
resource rate and set it to different values in different projectsand then
have an auto_open macro that overwrites StandardRate with local rate.
Unfortunately Cost1 gets set to zero when the project is reopened (I know
it's going to be because when I type something in it I get a warning message
- and it's not kidding!) . Bummer.
It actually seems to me to be a bug rather than a feature.
Related issue. When I do what I tried and save the project, it shows in the
Projects list with a cost based on my local rate. When I publish it, the
Project Center views show it with the 'local' cost but when I drill down into
the Project views it shows with cost based on the Standard Rate. This
implies that project server (or maybe Project Pro) is recalculating the task
level costs at the time the tasks are published or Project Server is doing it
at the time the Project view is generated. I thought Project Server just
stored the data it had been passed from Project Pro. Whatever - it means
that even if I could get the 'local rate' to work the way I want Project
Server would show a contradiction between what's visible at the Project views
from what's shown at Project Center. Another bummer.
I'd be interested in other opinions and particularly interested if you've
found a way to handle the different rates problem. It's likely to be a
show-stopper for us.
Denis