MSPro2007 Project Import Wizard creates user(s) for those set as l

[ST]

Hi,

When I use the MS Project Pro 2007 (SP1) "Project" Import wizard, I set
certain resources as "keep local with base calendar', yet MS Project Server
creates them as resources Server! After the import I see these 'local'
resources created on Server. They appear in the Resource Center, and can be
seen in 'Resources and Users' option within PWA's Server Settings > 'Delete
Enterprise Objects'. But, are are NOT visible in PWA's Server Settings >
Manage Users (Security Settings section).

In the Resource Sheet of the imported file the resource has been converted
to an enterprise resource (not local as was selected).

Is this a bug?

/Spiro Theopoulos.

 

[Dale Howard [MVP]]

ST --

If memory serves me correctly, a while back someone else asked the same
question, and I don't believe anyone answered it. Your question intrigued
me, so I just did the research. I think you are seeing an undocumented bug
in the system. I am using a Project Server 2007 instance with all updates
applied, including SP1, the Infrastructure Update, and the August cumulative
update. Here's what I have found:

1. In the Map Local Resources onto Enterprise Resources dialog, I select
the "Keep local with base calendar" option for every resource, and click the
OK button.

2. I click the Continue to Step 2 link.

3. On the Step 2 page (Confirm Resources), the system erroneously sets the
Import value for each resource to Yes, in spite of the "Keep local..."
option specified in the previous step. If the person importing the project
is only a member of the Project Managers group, the system will warn him/her
that he/she does not have permissions to create an enterprise resource. If
the person is a member of the Administrators group, however, the Yes value
in the Import column will cause the system to import the local resource and
convert it to an enterprise resource.

The way to avoid the problem is to manually set the Import value to No on
the Step 2 page and then continue on with the import process. If you have a
lot of local resources in the project, you can set the Import value to No
for the first resource and then use the Fill Handle to fill the No value for
every other resource. Specifying a No value in the Import column will leave
the local resources in the project as local resources, and not convert them
to enterprise resources.

Hope this helps.