I'm pretty new to Business Objects, so pardon me if this is a newbie question.

We've designed a reporting application we deliver to customers.  Previously we would deliver a universe and a linked universe.  The base universe (if that is the right term) would be where we would deliver upgrades, etc.  The clients would develop off the linked universe.  That way, as long as we did not make changes to the link points, our upgrades would not impact any client specific additions.

In our new world, we've started using contexts, which is causing us an issue since they would have to be re-built in the linked universe.

Has anyone ever dealt with a situation like this?  Is there a simple way we could separate our "model" product (to allow us to upgrade it) from "client" extensions?  Nothing is forcing us to use linked universes other than at the time it seemed the best solution/

Thanks for any guidance.

Hmm, if customers can develop their own additions, why are they not able to use contexts?
In any way, ADDING contexts within universes that support production can have severe repercusions (like splitting of generated SQL into multiple expressions)

Not sure though if I fully understand your issue..

Ties Blom
 

The issue is that when you link universes, contexts need to be built in the resulting parent universe.  So, if you make changes in one of the children, you likely have to rebuild contexts in the parent.  Andrew is trying to avoid that for his customers.

Steve Krandel
Intuit