Fixed mispelled name in ERP - won't synchronize to Sharepoint

[Matt Kennedy]

A resource had been added to the Enterprise Resource Pool (ERP) with her
first name misspelled. I corrected the name in the ERP. I checked a couple of
places in PWA and it now looked correct there. I then did a synchronize to
the project sharepoint site but it is still misspelled.

I next tried deleting the user from the shareppoint site using Manage
Sharepoint Sites > Go To Site Admin > Delete Selected User. I synchronized
again and it returned with the misspelling.

I then deleted the user from the sharepoint site again, then made a more
significant change to the users account in PWA (added Project Manager Group)
and synch'd again and still she returned with the misspelling.

Had a very similar issue with an email address that would never synch some
time back. Seems to me that this synchronization process between PWA and
Sharepoint is buggy and cumbersome at best.

Anybody else run into this or solved this?

Thanks,
Matt

 

[Reid McTaggart]

Have you republished the resource's assignments in her project(s)? I'm not
sure that this is the solution, but it's what I would try next.

 

[Jonathan Sofer - MCP]

I have seen the same issue myself. Once an account is synched with a site
it is stored in the WSS content database under UserInfo and there is
seperate record for each user per WSS site. Synching after the user has
been added seems to only synchronizes the permissions and nothing else.

As to your attempt to delete the user and then re-synch the PWA user, I have
seen the same issue here as well. There seems to be some cache or memory
that will load the old data if it recognizes the Windows User Account as
being added to the WSS site at some point in the past.

I do not have a good solution for you other than trying to run some SQL
updates on the UserInfo table in the WSS content database. A last resort.
But I hope that my same experience with this issue makes you feel more
comfortable that you are not seeing an environment specific issue.

 

[Matt Kennedy]

Thank you both for the replies. Jonathan you have confirmed my suspicion.
Seems like a pretty *significant* weakness in the product. This can really
cause problems when you are trying to take full advantage of the WSS
integration on a large project the way we are.

I can only hope that Microsoft is somehow made aware of this and can
correct/improve the synchronization process as it was the WSS integration
that swayed us to go with PS in the first place yet may also result in its
ultimate demise here.

 

[Eleanor]

How did you change the Resource Pool Name in Project Server? i can change
the account name within the users tool or within the SQL tables MSP-Resources
and MSP-Web-Resources; however, I cannot get to a table in SQL that changes
the Resource Pool Name.

-Eleanor

 

[Matt Kennedy]

If a user is both a resource (in the resource pool) and has a project server
account changing their name should update it in both places.

 

[Eleanor]

Wish it worked that way, but it did not. Any other ideas.

Thanks!
-Eleanor

 

[Matt Kennedy]

Just to clarify - when you open the resource pool using project professional
the name has not changed even though you changed it in PWA Admin? If that is
true than I would really have to wonder if the user you see in the resource
pool and the user you see in PWA Admin are really the same person/user. Not
sure what your situation is but if you can you might try deleteing the user
in pwa admin as a next step...