promoting applications from Dev using XMl and not deployment/copy on Analyst lib

[Ludi3]

Hi All,

I have inherited a Planning model from someone. The way the development is done is that Analyst libraries are only used in dev and they are synchronized with dev Contributor applications. Then the XMl from dev applications is imported into production applications. Production Analyst libraries are not used at al.

Any views on this process?

I would have gone for completely separate environments, copy Analyst libraries from dev to prod and synchronize prod applications with prod libraries.

Many Thanks

[SomeClown]

Like you mention, not the traditional method of deployment.  I don't see anything glaringly flawed with that approach.  The only snag is upgrading planning - you'd have to upgrade both environments before being able to promote changes (i.e. both dev and prod on the same version before moving up xml).

[Ludi3]

I suppose the only thing is you don't have the "original" Analyst libraries to fall back on.

[jeffowentn]

I've never seen it done that way.  If the concern is the business modifying the Analyst libraries, they could always deploy them to PROD but only give the Admins rights to the libraries. 

Jeff