|
Performing a Compare reports gets tricky many times and it could mess up the entire upgrade process it they are not done properly and the comparison reports are not understood properly. One should be careful when performing a database comparison on a predefined project. Before running each compare report, checking the compare options and change them or confirm them that they are checked or unchecked as per your requirement.
For example, say your project includes several records, panels, and menu definitions and you perform a database comparison just on panels only. All the panel definitions that were originally in the project will be removed and be replaced by any panel definitions found in the compare process. However, the record and menu definitions in your project will not be affected.
Performing a database comparison will also overwrite customized upgrade settings with the defaults for the specified target orientation.
There are two types of compare reports.
1) Compare all the database objects of the type specified and populate the current project with any objects defined differently in the source than in the target.
2) Only compare the objects in a particular project.
In both the cases, app Designer compares one object at a time.
When comparing objects in a particular project, it can be further done in 3 differnt ways.
1) Database Comparison.
2) Project Comparison.
3) Comparing Records
One of these methods was selecting objects by comparison. You do this by performing a database comparison, in which the current (source) database is compared with another database. Any objects defined differently in the two databases are added to the project.
If the objects are inserted into your project manually, and if one needs to see how those objects differ from the same objects in another database, one should perform a project comparison. This method compares only the objects in the project, and does not repopulate the project except in the case of record comparisons. Upgrade settings are never modified when you perform a project comparison.
When records are compared, during a database or project comparison, any differences found in record fields will be written into the project.
By default, when one performs a comparison, the system generates a report for each object type compared. These reports provide detailed information on how each object in the source differs from its counterpart in the target.
The Target Orientation option determines how the Upgrade check boxes in the upgrade definition window will be set for objects that were last modified by the customer in one database and last modified by PeopleSoft in the other database.
If you select the PeopleSoft Vanilla orientation, the Upgrade check boxes will be set so as to preserve PeopleSoft's changes. If you select the Keep Customizations option, the check boxes will be set so that your changes are preserved.
When you run the compare reports by date, the compare report check the date on which the objects were updated and by which user id.
When you compare the report with the version, especially for the tools upgrade, the objects are compared for the version to which it belongs.
|