S
Stephan Steiner
Hi
Since the documentation is somewhat lacking in that department, I searched
through this group and the project server one and figured out there are
multiple ways how I can create a summary task.
One is setting the summary task flag in a task, and the task immediately
thereafter will be a subtask of the summary task.
Another possibility it to set outlinelevel to 1 for the summary task, and
outlinelevel 2 for subsequent tasks so they will be grouped under the first
ask. However, that way the summary flag isn't actually set.
Yet another way is to set the summary field for task 1, then use the
outlinelevel (set it to 2), and voila.
The last one is using WSPs so that we have summary = wsp 1, subtask 1 = wsp
1.1 subtask 2 = wsp 1.2
It's even possible that multiple projects use the exact same WSP values,
which is what really bothers me.
Creating summary task and subtaks in project itself yields the following:
1) The summary task has the summary flag set
2) Outlinelevel of the summary task is 1
3) Outlinelevel of the subtasks is 2
4) WSP of the summary task is equal to its task ID
5) WSP of the subtasks are a concatenation of the task ID of the summary
task, a dot and the position towards the summary task.
However, since you cannot create a summary task, get its task ID, then
create the subtasks using PDS, I'm wondering what is the proper way to
create the following structure:
Summary
Subtask 1
Subtask 2
either via PDS, or via direct SQL if needs be (and in the latter case, which
SP should I call to ensure all the data is properly synchronized
afterwards).
And while I'm at it, would it be possible to create a Subsubtask1 that is a
part of Subtask 2?
Regards
Stephan
Since the documentation is somewhat lacking in that department, I searched
through this group and the project server one and figured out there are
multiple ways how I can create a summary task.
One is setting the summary task flag in a task, and the task immediately
thereafter will be a subtask of the summary task.
Another possibility it to set outlinelevel to 1 for the summary task, and
outlinelevel 2 for subsequent tasks so they will be grouped under the first
ask. However, that way the summary flag isn't actually set.
Yet another way is to set the summary field for task 1, then use the
outlinelevel (set it to 2), and voila.
The last one is using WSPs so that we have summary = wsp 1, subtask 1 = wsp
1.1 subtask 2 = wsp 1.2
It's even possible that multiple projects use the exact same WSP values,
which is what really bothers me.
Creating summary task and subtaks in project itself yields the following:
1) The summary task has the summary flag set
2) Outlinelevel of the summary task is 1
3) Outlinelevel of the subtasks is 2
4) WSP of the summary task is equal to its task ID
5) WSP of the subtasks are a concatenation of the task ID of the summary
task, a dot and the position towards the summary task.
However, since you cannot create a summary task, get its task ID, then
create the subtasks using PDS, I'm wondering what is the proper way to
create the following structure:
Summary
Subtask 1
Subtask 2
either via PDS, or via direct SQL if needs be (and in the latter case, which
SP should I call to ensure all the data is properly synchronized
afterwards).
And while I'm at it, would it be possible to create a Subsubtask1 that is a
part of Subtask 2?
Regards
Stephan