Schedule with macros and tool bars....

[Eric_H]

Ok, we are new to the Project Server world. We have an old schedule that has
evolved through the ages and it has many macros, custom fields, views and
toold bars with it. when we try to save it to our server and pull it back
out, many of those customizations are either gone or no longer work. We are
trying to avoid putting all of those macros, fields, views and toolbars in
the Enterprise because none of our other planners will need them and it makes
the Ent Global file huge, slowing performance. Also we have tried to copy
those modules, tool bars, etc. to the file in organizer, but some things
won't copy correctly anyway. What am I doing wrong?

 

[Jack Dahlgren MVP]

The Toolbars need to be in a global file to work.
I think that either the local global or enterprise global should be
sufficient.
The best practice is to create a new toolbar which has it's own name rather
than adding commands to an existing toolbar.
I think you are going to find it easiest to make it work in the Enterprise
global despite your desire not to.

There is no way to know exactly what you are doing wrong, but I'd suspect
that you are not correctly referencing tables and fields and modules and
macros. It can be difficult to keep them straight when you have multiple
versions. Conflicts between local and enterprise fields are also possible.
Start small with one item then work methodically through them all. For
example, moving a toolbar to the Enterprise global is takes a few different
steps. First the fields need to be created in the enterprise global. Then
project needs to be closed and restarted to pick up the new fields, Then the
macro needs to be converted to use those fields and saved into the checked
out enterprise global. Then project needs to be exited and restarted, then
you can create a toolbar which references that macro. Then project needs to
be closed and restarted again to pick up those changes in the enterprise
global. I also find it helpful to use a configuration spreadsheet which
notes which fields are used and for what purposes. Which filters exist,
which views exist etc. It could take a while to sort it all out.

-Jack Dahlgren

 

[Eric_H]

Thanks Jack, I'll try it tomorrow...

The Toolbars need to be in a global file to work.
I think that either the local global or enterprise global should be
sufficient.
The best practice is to create a new toolbar which has it's own name rather
than adding commands to an existing toolbar.
I think you are going to find it easiest to make it work in the Enterprise
global despite your desire not to.

There is no way to know exactly what you are doing wrong, but I'd suspect
that you are not correctly referencing tables and fields and modules and
macros. It can be difficult to keep them straight when you have multiple
versions. Conflicts between local and enterprise fields are also possible.
Start small with one item then work methodically through them all. For
example, moving a toolbar to the Enterprise global is takes a few different
steps. First the fields need to be created in the enterprise global. Then
project needs to be closed and restarted to pick up the new fields, Then the
macro needs to be converted to use those fields and saved into the checked
out enterprise global. Then project needs to be exited and restarted, then
you can create a toolbar which references that macro. Then project needs to
be closed and restarted again to pick up those changes in the enterprise
global. I also find it helpful to use a configuration spreadsheet which
notes which fields are used and for what purposes. Which filters exist,
which views exist etc. It could take a while to sort it all out.

-Jack Dahlgren