PSI Updates vs. Project Updates

[Bryant Likes]

Okay so I knew that the events that were called were different between the
two.

Project Update -> Project Saved Event
PSI Update -> Project Updating Event, Project Saved Event, Project Updated
Event

But something that doesn't make sense to me the that if you update a project
via the project client the project's mod_rev_counter in the msp_projects
table gets incremented as well as the task's mod_rev_counter. However, if
you make the same change via the PSI only the task's mod_rev_counter gets
incremented. Not a huge deal but causing me some headaches when tracking PSI
updates.

Is this by design or is it a bug of some sort?

 

[Martin Winzig]

i think thak microsoft statement will be:
======================
Our current view is that this software is working as designed.
"By design", does not necessarily mean that a particular feature has been
explicitly designed in such a manner as the way in which it behaves. It is a
more generic term. It may be better put by stating that, due to the inherent
design of the product, the behaviour of a particular feature is behaving as
expected, ergo it is "By design". As is with each and every piece of
software, every eventuality cannot be accounted for in the design stage. So,
similarly, for something that may not have been accounted for in the original
design of the product/feature, but is still behaving as would be expected,
this would be deemed as being "by design".
For something to not be by design, then this would mean that a feature had
been explicitly designed in a certain way and that the subsequent behaviour
does not match that design requirement.
===============================
By the way i think that this standart ansver is in this case correct.

http://projectserver.cz/cms/index.php?itemid=39

Regards Martin winzig

 

[Chris Boyd]

Don't be so quick to judge us. Not all bugs are closed “By Designâ€. We have
made many fixes to Project 2007. A good chuck of fixes in SP1 comes from
customers who report issues.

Bryant, thanks for reporting this issue! Can you provide a bit more details?
Which DB are you reading the rev counter from?

--
Chris Boyd
MS Project
Program Manager

Blog: http://blogs.msdn.com/project_programmability/

 

[Bryant Likes]

[snip]

Bryant, thanks for reporting this issue! Can you provide a bit more
details?
Which DB are you reading the rev counter from?

Sure!

Maybe it is just the way I'm updating a project. However, here is how you
can reproduce it.

If you create a project and add three tasks to it you will end up with
something like:

Project A - mod_rev_counter = 1
Task 1 - mod_rev_counter = 1
Task 2 - mod_rev_counter = 1
Task 3 - mod_rev_counter = 1

Next open the project using project client and make a change to task 2 and
then save the project. You will get:

Project A - mod_rev_counter = 2
Task 1 - mod_rev_counter = 1
Task 2 - mod_rev_counter = 2
Task 3 - mod_rev_counter = 1

This is what I would expect. The project's mod_rev_counter gets incremented
since one of its tasks has changed.

Now modify task 3 using the PSI. You will get:

Project A - mod_rev_counter = 2
Task 1 - mod_rev_counter = 1
Task 2 - mod_rev_counter = 2
Task 3 - mod_rev_counter = 3

This is not what I expect. The task gets a mod counter increase the project
does not. I would expect the project's mod_rev_counter to equal 3 as well.

The reason this is an issue for me is that when a project save event happens
I was checking the project's mod_rev_counter and then using that number to
query the database for all the changes in that rev. This worked great when
changes were done through the project client, but PSI changes didn't work
because the mod_rev_counter was not incremented.

Does this make sense?

Thanks!