"Save interim plan" behavior

G

greghoro

I'm trying to figure out the logic behind the "Save interim planâ€
functionality.

What I have observed. When I use this to copy Baseline into Baseline1, is
that it does a one for one copy of all Baseline data (work, dates, cost,
duration) into its corresponding Baseline1 field for each task in the Table
area of a usage view.

However, the Timescaled data that is copied into Baseline1 Work is the
current value for Work and not Baseline Work as I would have expected. This
results in a situation where the Timescaled side may not add up to the Table
side for a task.

Is there a logical explanation for this behavior?

Greg

Is there a locgical explanation for this behavior?

Greg
 
M

Mike Glen

Hi greghoro ,

Try posting on the server newsgroup as this one is closing down. Please see
FAQ Item: 24. Project Newsgroups. FAQs, companion products and other useful
Project information can be seen at this web
address:http://project.mvps.org/faqs.htm .

Mike Glen
Project MVP
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

"Save interim plan" behavior 1
Question on Saving Baselines 10
saving an interim plan 5
Copy/Paste data into Baseline vs. Baselining 3
Comparing start and finish information w/Baselines and Interim pla 2
Baselining postpones the start of leveled tasks?! What's happening? 1
Project Online Timesheets Actuals Mismatches - data not publishing to projects 0
Time scaled Baseline does not roll up 5

Top