dates change after plan insertion

[chris_culley]

Hi,

I don't even know where to start with this, so any help would be
appreciated!

I am loooking after an MSP plan which is comprised of a series of
other, lower level, plans inserted into it. After insertion, one of the
lower level plan's dates all change - by about two years. I have no
idea why, and am not sure where to start looking.

Originally I thought it might be due to the plans having different
start dates, but I've corrected this, and the same still happens.

Does anyone have any ideas?

Thanks in advance,

chris

 

[Rob Schneider]

Hi,

I don't even know where to start with this, so any help would be
appreciated!

I am loooking after an MSP plan which is comprised of a series of
other, lower level, plans inserted into it. After insertion, one of the
lower level plan's dates all change - by about two years. I have no
idea why, and am not sure where to start looking.

Originally I thought it might be due to the plans having different
start dates, but I've corrected this, and the same still happens.

Does anyone have any ideas?

Thanks in advance,

chris

Are there links (successor or predecessor field) between projects which
cause this?

I'm also curious ... you infer the plan exists, but you mention
"inserting" the projects from one into another. I would have thought
that it already has been inserted, and wonder why you have to do it
gain. Does this have something to do with what's going wrong.

And exactly what dates are changing? Start, Finish, baseline dates, ...
which ?

 

[chris_culley]

thanks Rob - appreciate that the OP didn't have much useful information
in it...

I've got a programme constructed of a few workstreams, each maintaining
their own plans... for example, an IT workstream, a commercial
workstream, a legal workstream etc etc...

I want to consolidate all these into *one* MSP plan, against which I've
got a number of macros and tools that I use to extract useful bits of
"programme" information...

The "programme level" plan is, therefore, an empty MSP plan, with a
number of subplans inserted into it - I've done this before and know it
can work, and seems to be a useful thing to do..

However! at least one of the plans has its finish dates change once it
is inserted. It's not simply a case of the "summary" (ie bold) task
aligning it's finish date with the end date of the project, but actual
tasks and milestones are having their dates change.

I've tried to debug this, and have noticed the following:
- when the plan in question is inserted on it's own, no dates change
- when a second plan is inserted, the dates on the first change.

It's not a case of links between plans, nor of different starting dates
on the plans - I am at a complete loss as to what else it could be.

Any light to be shed would be fabulous!

Cheers

Chris

 

[chris_culley]

OK fixed this.. it was quite simple in the end...

For tasks that had already been started when the workstream plan was
constructed, the owner hadn't written in a date - merely left it as the
start date of their plan.

Thus, when it was imported into the consolidated plan, the task start
date reverted to *that* plans start date - throwing everything out of
whack..

annoying to track down!

Chris