PSI Updated Resource Cost not showing in plan

[ProjectBob]

Hi,

I have used UpdateResources to update an enterprise material resource
RES_STD_RATE. Once the update completes the dataset shows the new value, the
published Resources table in SQL shows the updated value, and when you view
the resource in the resource centre in PWA it shows the updated value.
However, if I then open the resource in Project it shows the old resource
value, and likewise when I open a plan that uses the resource they show the
old value also. Is there a step I have to use after the UpdateResources to
make sure that the resource global is updated which filters down into all
plans?

Thanks

 

[Bryant Likes]

Hi,

I have used UpdateResources to update an enterprise material resource
RES_STD_RATE. Once the update completes the dataset shows the new value,
the
published Resources table in SQL shows the updated value, and when you
view
the resource in the resource centre in PWA it shows the updated value.
However, if I then open the resource in Project it shows the old resource
value, and likewise when I open a plan that uses the resource they show
the
old value also. Is there a step I have to use after the UpdateResources
to
make sure that the resource global is updated which filters down into all
plans?

We've ran into some issues like this with moving dates. The only way I was
able to resolve it was to compare all the fields in the record before and
after the Project Client update (which I assume would set it correctly) and
then make sure to set as many of the fields as possible. For milestone dates
we actually have to not only set multiple fields, but set them twice via the
PSI for them to "stick" in Project Client.

 

[ProjectBob]

Hi Bryant

Thanks for your reply. I have been having a look in the project cache and
notice the folder for my login contains a file global[1].mpc. I have tested
with moving this folder out of the cache. When I do it seems to refresh the
global and the new cost information is updated, with my folder being
recreated in the cache. Is it possible to access the enterprise global from
PSI at all?

Could you please explain a little bit where you say "compare all the fields
in the record before and after the Project Client update (which I assume
would set it correctly) and then make sure to set as many of the fields as
possible"

Thanks

 

[Bryant Likes]

Hi Bryant

Thanks for your reply. I have been having a look in the project cache and
notice the folder for my login contains a file global[1].mpc. I have
tested
with moving this folder out of the cache. When I do it seems to refresh
the
global and the new cost information is updated, with my folder being
recreated in the cache. Is it possible to access the enterprise global
from
PSI at all?

Not sure. Sorry.

Could you please explain a little bit where you say "compare all the
fields
in the record before and after the Project Client update (which I assume
would set it correctly) and then make sure to set as many of the fields as
possible"

Sure. It sounds like you're setting a single field on the project data set
and then saving it using the PSI. What I'm saying is that even though at
field might change, there could be other items in the record that also need
to change in order for project client to pick up the change. So I would try
making the same change using project client and compare the results of what
gets changed in the database to the what you're seeing change when you use
the PSI.

Does that make more sense?

Let me know.

 

[ProjectBob]

Hi Bryant

Great advice thanks, I have been comparing the rows in the resource table
after updates from PSI and updates from PWA. It looks like when you update
from PWA, these columns in the resource table are updated

REV_NEXT_SEED = +2 of current value
RES_CURRENT_REV_COUNTER = current value of REV_NEXT_SEED
MOD_REV_COUNTER = current value of REV_NEXT_SEED

These columns remain the same when the update is done in PSI. I notice
that, if I do an update in PSI and then change the values in the columns via
a SQL query, it updates the global template to show the new cost value.

The only thing is now though, I can't seem to find these columns in the
DataSet, so the only thing I can think of to update this is to use a SQL call
after the PSI method. I thought though that the whole point of PSI was to
provide an interface so that a developer would not be accessing and changing
the SQL tables directly?

Thanks

 

[Bryant Likes]

[snip

These columns remain the same when the update is done in PSI. I notice
that, if I do an update in PSI and then change the values in the columns
via
a SQL query, it updates the global template to show the new cost value.

The only thing is now though, I can't seem to find these columns in the
DataSet, so the only thing I can think of to update this is to use a SQL
call
after the PSI method. I thought though that the whole point of PSI was to
provide an interface so that a developer would not be accessing and
changing
the SQL tables directly?

Yes you can't (or don't want to) update the tables directly. That sounds
like a defect to me that Microsoft should take a look at. When you update
the table, the mod_rev_counter should automatically increment.

One other possible work around for this would be to update something else in
the table via the PSI that does increment the mod_rev_counter and then do a
second update to revert that change back. This would cause your actual
change to get picked up.

Does that make sense?

We do something similar in our case.