K
Kurt Petteloot
We're currently working on a Project server 2003 implementation. We've
created several custom fields, views and some macro's in our own
development/test environment. Now we want to port these customizations over
to the test environment at the customer's site. In order to accomplish that
we made a backup of the global template from our dev project server and
restored that file onto the customer's environment.
This is an approach we use regularly to migrate customizations from one site
to another. Only this time the custom enterprise fields are not imported into
the customer's project server. Views, Tables, macro's are all ok, but the
custom enterprise fields just won't come in.
To verify that the problem was not with the global template we tried
restoring the same file onto some other project server environment and it
worked perfectly well. So our guess is that it must have something to do with
the setup/configuration of the customers' project server environment.
Can anyone give us a clue on what may causing the import of the custom
enterprise fields to fail? For sake of completeness i can tell you that both
Project Server as well as the Project Professional client run on SP2.
Thanks.
Kurt petteloot
created several custom fields, views and some macro's in our own
development/test environment. Now we want to port these customizations over
to the test environment at the customer's site. In order to accomplish that
we made a backup of the global template from our dev project server and
restored that file onto the customer's environment.
This is an approach we use regularly to migrate customizations from one site
to another. Only this time the custom enterprise fields are not imported into
the customer's project server. Views, Tables, macro's are all ok, but the
custom enterprise fields just won't come in.
To verify that the problem was not with the global template we tried
restoring the same file onto some other project server environment and it
worked perfectly well. So our guess is that it must have something to do with
the setup/configuration of the customers' project server environment.
Can anyone give us a clue on what may causing the import of the custom
enterprise fields to fail? For sake of completeness i can tell you that both
Project Server as well as the Project Professional client run on SP2.
Thanks.
Kurt petteloot