Getting rid of differences in linked projects - confirm my solutio

[Michelle Moulliet]

I have several projects in my server with dependencies to other projects.
When I open some of them, the predecessor & successor tasks do not always
display the right date. I did a little investigation and found that for the
tasks that were not showing the right date, there were differences noted in
the project links dialog box in the predecessor & successor tabs.

I think I figured out how to fix the fact that updates are not being
automatically imported into the file & causing the differences notification.
I went to Tools>Options>View and deselected the Show Links Between Projects
Dialog on Open box & selected the Automatically Accept New External Data box.
This seemed to fix the situation so that I no longer see the dialog box and
the updates are automatically imported. Is this right? It seems like it's
working. Thanks for verifying for me.

 

[Dale Howard [MVP]]

Michelle --

The default options for cross-project linking require the PM to accept the
schedule changes manually. That is why you saw the dialog and that is why
the changes were not accepted. You have not set the option to update the
changes automatically, which will also work just fine. As long as your
solution works for you, who can argue with success?

 

[Michelle Moulliet]

How right you are. It still seems to be working.

Is there a way that I can change the default option in my global? I've
changed it in my enterprise global and I thought I changed it in my local
global; but I made a new project and the settings remain with the default
manual change admission. Is this setting local only to the files and not to
the client? If not, any idea why it's not saving to my local global or why
the enterprise global isn't overwriting my local?

Thanks!

 

[Dale Howard [MVP]]

Michelle --

Every user must change this option individually in their Options dialog.
You CANNO set this option globally by opening the Enterirpse Global file and
setting the option there. The Enterprise Global file is your organization's
"library" of enterprise custom Fields, Views, Tables, Filters, Groups, etc.
You cannot use it to set any options on each user's Options dialog EXCEPT
for the default currency. Hope this helps.

 

[Michelle Moulliet]

Dale,

Thanks. OK, I understand your point regarding the enterprise global.

But when I set my options in my client, why didn't it save the change to the
global template local to my client? The next time I opened my client I
expected the option to be selected, it was not.

Why did making this change only save to the specific file that I had open
when I changed it? Is the setting local to the file rather to my client?

Thanks again.

 

[Dale Howard [MVP]]

Michelle --

Excellent question!

In the Options dialog, notice that the Cross-Project Linking options are
only for the active project. Notice also that there is no "Set as default"
button for those options. This means you must set these options for each
project individually. Hope this helps.

 

[Dale Howard [MVP]]

Tim --

No, that will not solve the problem. The Enterprise Global file is like an
organization's "library" of custom objects, such as Fields, Views, Tables,
Filters, Groups, Calendars, etc. It cannot be used to globally set Options,
with the exception of the default Currency value on the View page. Hope
this helps.

 

[Reid McTaggart]

Yes.

Since the setting goes with the project, if you create a project template
with this setting, then any project created from the template will have the
setting.

--
Reid McTaggart
EPM Architect
Microsoft

 

[Mike]

Michelle
The link between projects dialogue box is there for a purpose. It
flags conflict. Automatically accepting such changes hides this
conflict from the plan owner. Most project managers I know would not
accept such change without prior notification / discussion.

regards

Mike