Why are there two projects for each migration in the target database?
When we do a migration through Phire, in the target database we find both the original development project and the Phire-generated project. Is the behavior normal? And which project represents what was migrated?
Admin said,
February 1, 2016 @ 5:57 pm
When Phire performs the migration it generates a project that encapsulates the objects that were ultimately migrated and the actions performed. Included in list of objects may or may not be the project(s) that were used in development to create and customize the individual objects. So the truest record of what was migrated would be the Phire-generated project, and in fact, that’s the project Phire uses to perform the Project Build if requested.
Phire is designed so that a Change Request could contain one project, multiple projects, a subset of the objects from a project, or even no project at all. When importing the objects the developer may choose to not import the original development project as an object to be migrated along with the contents. For all these reasons, it’s necessary for Phire to generate a project that reliably contains exactly what was migrated. If the developer chose to include one or more project objects in the object list, then they would be migrated as well.
This question often comes up when users rely on searching for project definitions in the target database to prove what was migrated. This reflex is a holdover from times before Phire was being used to perform the migrations. Once Phire is in control of the migrations, this information and much more is available in the on-line pages, or in the reports created from the Phire data.