Resources changing to local resources:MSP07 SP2

[Quizzed again]

Using MOPS2007 SP1 and Feb CU. Client SW has SP2.
We must save files offline to manipulate with other SW. The other SW does
not recognize enterprise fields. No way around that.

I have a macro that copies enterprise custom Task field values to
non-enterprise Task fields. Works great with custom Task fields.

However for resource fields the first copy & paste of enterprise custom
resource field data to a non-enterprise resource field does not paste
anything but instead it changes the enterprise resources to local resources.
The second paste (ctrl-V) will actually populate the non-enterprise field
with the copied value.

When save is selected, the user is prompted to replace the local resources
with Enterprise resources. Selecting Yes to that clears all the values from
the non-enterpise resource fields! (This replacement is to prevent having
local resources).

So as long as the resources are local then they can have local custom
resource fields with data. When the project uses enterprise resources the
resources cannot have non-enterprise custom fields with data in them.

I am curous:
Is this specific to SP2 in the client SW?
Why can I create non-enterpise fields for resources but not populate them
when the file is online (ie, enterprise)?

Side note, I tried to install, and failed, the SP2 on my 3 servers. I had
the system restored but I have not re-installed my local client so that is
why the SP does not match the server.

 

[Jonathan Sofer [MVP]]

This "feature" is not specific to your version, it has always been the case
in both 2003 and 2007. Local fields against enterprise resources will not
retain information. It is due to the way they designed the system. The
server always resets all the resource related information with the
enterprise version including local fields each time you replace a local
resource with an enterprise and each time the project plan is opened on the
server as well.

So your local resource field data will always be wiped out when dealing with
Enterprise Resources.

Sorry to be the one to give the bad news.

Jonathan

 

[Quizzed again]

Nice job MS.
Thank you Jonathan.

This "feature" is not specific to your version, it has always been the case
in both 2003 and 2007. Local fields against enterprise resources will not
retain information. It is due to the way they designed the system. The
server always resets all the resource related information with the
enterprise version including local fields each time you replace a local
resource with an enterprise and each time the project plan is opened on the
server as well.

So your local resource field data will always be wiped out when dealing with
Enterprise Resources.

Sorry to be the one to give the bad news.

Jonathan

 

[Jonathan Sofer [MVP]]

You might get away with setting the value at the resource assignment level.
This assumes all your resources have assignments.

 

[Gary L. Chefetz]

Not sure where you're going with this, but have you considered dumping the
info into Excel?

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[orobla]

Hi,

I have converted a workplan from 2003 to 2007 and in the 2003 the workplan
had enterprise resources with local custom fields. When the workplan is
converted the local custom fields are lost and I cannot copy and paste the
2003 local custom fields into 2007 converted workplan.

2003 allows non-enterprise custom fields at resource level for resources in
the resource pool. How can I add a non-enterprise custom field in 2007 to
paste this information from 2003?

Thanks & Regards

Oscar

 

[Jonathan Sofer [MVP]]

Oscar, I have to disagree with you. I don't believe 2003 allows
non-enterprise custom fields at resource level. They would get wiped out
on each resource pool synchronization which happens on project open.

 

[orobla]

I didn't know it either and I believed that this was not possible until I
have seen it. Do you think that this is an error in our 2003 installation (we
have only SP1 installed)? Do you recommend me to open a ticket to Microsoft
about this conversion issues from 2003 to 2007?

Thanks & Regards,
Oscar

 

[Gary L. Chefetz]

Oscar:

When you say you "converted a workplan" what exactly do you mean? If you
mean you simply opened it Project 2007, then I think you need to look at the
Import Project to Enterprise function Under Tools > Enterprise options,
which will allow you to map local field values to Enterprise field values.
If you're trying to move both the resources and the plan into the enterprise
environment, you should always import the resources and their values first,
then import the schedule.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[orobla]

Hi Gary,

I saved the 2003 workplan in xml and then I opened it in 2007. Before
opening the workplan in 2007, all resources that had assignments in the
workplan were created in 2007. When I saved the workplan to the 2007 server,
the resources were replaced by the existing ones in the resource pool.
However the custom fields at local level of course were not saved. After
saving the workplan to the 2007 server I had to transfer via the Organizer
the custom fields, views, groups, tables, custom lookup tables from the 2003
workplan to 2007. The only problem I have is with the custom local fields at
resource level. I haven't been able to transfer them to 2007 since in 2007
all custom fields at resource level for resources in the resource pool are
not editable. Are the custom fields at resource level only valid for local
resources in 2007?

Regards,
Oscar Robla

 

[Jonathan Sofer [MVP]]

Yes. And I am surprised that you say that this is not the case in your 2003
environment. Out of curiosity, what release of 2003 are you on?

Jonathan