Project Import

Import and compare PeopleSoft XML project files against the target database to review object states and perform PeopleCode/SQL diffs.
Categories:
Tags:
Tailored Operational Context
  • Target Database: —
  • Context Type: —
  • Alert Severity: —
  • Triggered Time: —
  • Firing Context: —

What It Is

Project Import lets you upload an XML export file of a PeopleSoft project (the .xml files exported from App Designer via Tools -> Copy Project -> To File).

This lets you inspect the contents of a project file (including embedded PeopleCode, SQL, and HTML definitions) and compare it against any of the configured databases before actually migrating or importing the project into the environment.

Uploading a Project XML

URL: /project-import

To import a project:

  1. Go to the Project Import page.
  2. Click the file upload box or drag-and-drop your PeopleSoft project XML file (up to 25MB).
  3. The server will parse the XML and add the project to your local imports history list.

Project XML View

Once imported, you are presented with the Project XML View:

  • Metadata Summary: Shows the source database where the project was exported, export date, export Operator ID, and file stats.
  • Flat Items List: A single flat table listing every object in the project, categorized by type (Record, Field, Component, etc.).
  • Source Code View: Items that contain code (PeopleCode, SQL, or HTML) are marked with an icon. Clicking on these items will expand them inline to show the source code directly in your browser.

Database Comparison

You can compare the imported XML project against any of your active databases:

  1. Select the target database from the dropdown in the comparison card.
  2. Click Compare.
  3. psLens runs a comparison check for each object:
    • PeopleCode: Performed via content hashing (ignoring line endings and trailing whitespace) to determine if the code is identical or different, since timestamps are often unreliable across migrations.
    • Other Objects: Performed via the LASTUPDDTTM timestamp on the target database table.

Compare Statuses

  • Same: The object in the XML file is identical to the one in the target database.
  • Different: The code contents differ between the XML and the database.
  • DB Newer: The object in the database has a newer timestamp than the one in the XML.
  • DB Older: The object in the database has an older timestamp than the one in the XML.
  • Not in DB: The object does not exist in the target database.
  • No DB Lookup: The object type is not supported for automatic database comparison.