Dear all,
I am checking the work with portfolios.
As far as I understand, the mechanism is as follows
- When you add project to portfolio and then consolidate projects, Spider considers all object except activities to be the same in different projects as long as they have the same code (resources, skills, multi-resources, materials, material sets, cost components etc.). So far activities is the only object I have found, which Spider would prefix with the project code when consolidating and then would remove this prefix when distributing back.
- Spider does not do any verification on whether objects, which have the same code are actually exactly the same.
- As far as I can see, the objects of the project, which is added first to portfolio take precedence (e.g. if ResA in Project1 has a Calendar 2 and ResA on Project2 has a Calendar 1, then when consolidating projects, if Project1 is added the first one to the Portfolio, then ResA will have Calendar2 both in Project1 and Project2, once the projects are distributed back).
I think therefore, that there must be some extremely strict discipline imposed in practice to insure, that such conflicts would not happen. So logic says, that there should be only single place, where it would be allowed to change parameters of the objects, which can be shared between projects (calendars, resources, etc).
Question:
- Without central server, how does it work on practice? How is this disciplene imposed?
Regards.
Evgeny