Archives

If you try to monitor changes to your PeopleSoft application,
you have probably encountered many situations in which an object
is marked as changed, but the user whose ID is shown on the
object doesn't remember changing it. This seems to affect
pages more than most other object types.

In a previous post I mentioned one possible reason. Open a
page and select the "Order" tab and then double-click
on one of the fields to view its properties. Even if
you make no changes and cancel out of the dialog, the page
is still considered "changed". This is not a problem if you don't
hit the "save" button. However, if you make changes to other
objects and then save the project, and that page is still open,
it gets saved along with the rest of the objects. Your ID
is then shown as having changed the page.

Seemingly unrelated changes can cause a page to be considered
"changed". For example, if you open a field object and mark
a different
label as the default label for the field, it will cause all
of the pages containing that field to appear to be changed
when you run compares. Since the field is a separate object,
we might think that the page object would not be affected,
but it is. PeopleSoft once delivered a Global Payroll update
that included a change to a field's default label. Unfortunately,
that field was used in many places outside of GP. Open one
of those pages and it's suddenly considered changed.

Couldn't we see the reason using the compare reports? I don't
know about you, but I've always found some of these reports,
including the page reports, very difficult to read. One small
change to a page can result in a huge compare report. What
causes this? Well, the report tries to match fields based on
the field order on the page—in other words, it uses the order
as a key for the comparison. That means that moving, adding
or deleting one field can cause many other fields to be marked
as changed. If a page compare report is incomprehensible and
you really need to understand the differences, you could go
into your SQL tool and select from PSPNLFIELD, sorting by
RECNAME, FIELDNAME and then FIELDNUM instead of just FIELDNUM.