S
Scott McClure
A bit ago I asked about the icon or indicator for a need
to publish changed assignments not going away with
publishing. It turns out that, because our resources are
generic, the indicators will not go away.
We use generic resources because we are scheduling shop
mechanics over fairly long projects and we don't want to
try to predict which of 30 guys will be assigned to a
particular job. Nor do we want to try to actually assign
these guys when the shop chief puts them on a particular
task (lower level of detail than the task in the
project). I think using generics is right for us.
My questions: is it any kind of problem to simply leave
the indicators? MS suggests changing these resources
to "real" and publishing. Does this present any problems
and could we then change them back? Would it be possible
(and simpler) to find a field in the back end to change?
Would anyone know what field that may be?
Thanks
to publish changed assignments not going away with
publishing. It turns out that, because our resources are
generic, the indicators will not go away.
We use generic resources because we are scheduling shop
mechanics over fairly long projects and we don't want to
try to predict which of 30 guys will be assigned to a
particular job. Nor do we want to try to actually assign
these guys when the shop chief puts them on a particular
task (lower level of detail than the task in the
project). I think using generics is right for us.
My questions: is it any kind of problem to simply leave
the indicators? MS suggests changing these resources
to "real" and publishing. Does this present any problems
and could we then change them back? Would it be possible
(and simpler) to find a field in the back end to change?
Would anyone know what field that may be?
Thanks