Resource Issues

[Shane]

We're having some issues when making changes to resource names. Example, we
use a group to represent multiple people, lets call it IM.Arch. Because of a
contract change, we need to change the name to IMIT.Arch. I open the
Enterprise Resource Pool and simply add the "IT" to the name. Everything else
remains the same. Once saved, I'm able to see the change throughout the
system, including the team builder, the user account in Web Access, etc. Even
existing assignments in MS Project reflect the change.
However, there is one place where the change does not show, the Resource
Center in Web Access. There, it still shows as IM.Arch. The change even shows
up in the "View Resource Assignments" page, but not in the Resource Center.
This is also an issue with new resources added to the resource pool.
Where does the Resource Center get its information and why doesn't it
reflect the changes I make like everywhere else in the system? Does it rely
on the OLAP cube? Could there be something amiss there? The OLAP cube seems
to be generating every night like expected. On the webpage where you manage
the OLAP cube, it indicates when the process was initiated, but doesn't let
you know if it finished correctly.
Any suggestions?
- Shane

 

[Geoff Vernon]

Hi Shane,
Any change made to the enterprise global, enterprise resource pool or any
particular project schedule will not display in PWA until after you have
pushed it through by selecting Collaborate, Publish, All Information.
Have you done this?
Cheers.....Geoff

 

[Shane]

Geoff - it's possible to push a project through re-publishing, however, it's
not possible to do the same for the enterprise global template or any
enterprise resource. When you open the enterprise global template, these
options are grayed out. Same for when opening any resource from the
enterprise resource pool.

After further research, I found a problem with our OLAP cube. I'm looking
into it now.

Thx

 

[Gary L. Chefetz [MVP]]

Shane:

I can't say for certain, but the resource publish routine may very well get
kicked off when the resource availability refresh runs with the OLAP cube
job. Unfortunately there's no way to kick this off for resources like there
is for project plans, but you can also trip it by changing things like
enterprise outline code values and other fields. The strategy here is to
change a code value to bad data, and then save. Open it up and change it
back an then save.