I'm about to embark on a project with a team of 5 people in two locations. Although there is one main FM administrator, there is a chance that the other two could occasionally need to make small changes in FM too.
Whats the best practice for avoiding conflicts in FM usage in this environment? There appear not to be any warnings when more than one person has the model open. The customer does not have a source control application to integrate.
Any suggestions?
You could download the CSV source control software for free - this would be better than no source control where one developer could overwrite another's work.
Regards,
MF.
We had a multi-developer model at a client and it all worked because we had a "Model Manager" assigned, to basically control the "Master" model. When one of the developers was going to work on the model, the Model Manager would create a copy of the Master (Working Model) and removed portions of the model that were not pertainent to this developer's forthcoming effort.
Once the developer was complete, the Model Manager would run the scripts from the Working model's log, against the Master Model. The working model was then archived, with date, time and brief description of its purpose.
Worked well.
Hello, I would agree with the opinion to get a version control system in place as your first goal. You are also going to look up the concept of 'segmented models' within FM. FM's own help files should have some info on this, and if you have a support account then Cognos has a Best Practice doc on this topic.
Hi ,
The best method to handle this case is to use brannching and merging opiton in Framework manager..
Thanks,
Nirmal.