The type setting 65 sets this item as an “authoritive upper node” that is associated with a blob.

So in this case each corporate activity, audit etc has its own blob where as a Phase for example doesn’t as 65 is not set for this.

He consequence is that a predecessor of a dependency in one blob doesn’t automatically update a successor of the dependency in another blob.

What you need to be careful to not do is set 65 for two items that are both in the same hierarchy (eg Group and Corporate Activity) since causes problems with baselines. (The Audit and sub IS audit have been designed as a special case that allows this.)

A bit technical but hope that makes sense.

Posted in: eTrack FAQ, Timesheet