Hey all,
How do you manage to do model deployments in 2012 when moving code from TEST to STAGING when there are multiple projects in multiple states? Eg. during a large scale implementation.
eg. Client has DEV, TEST, STAGING, and PROD environments.
Client dev exported project A and project B from DEV to TEST via XPO.
In TEST, Project A has been validated by the SME, project B has yet to be tested or had an issue.
Client wants to move project A to PROD.
So project A and B are in the same model in TEST. How do you move project A to STAGING without moving project B?
Are devs required to create a separate model for each customization they do? Even if that's true, aren't objects only assigned to one model? What if two projects modify the same object? This has always seemed crazy when there's multiple xpos touching multiple objects that frequently overlap.
Is there even any risk to doing XPO deployments to STAGING if you're doing modelstore deployments to PROD? All of the existing element IDs should stay intact and any new element IDs will not conflict with prod, unless I'm missing something?
Model deployments seem fine for ISV solutions and whatnot, but I've never been able to figure out how they fit into the standard end-user implementation and support scenarios...
