PeopleTools upgrade - issues with "Invalid Views" steps
We are in the midst of upgrading from PeopleTools 8.59.23 and PeopleSoft Financials 9.2 PUM 50 to PT 8.61.11 and FSCM 9.2.053. During the Test Move 1 PeopleTools upgrade, the "Creating the Invalid Views" step encountered 1300+ warnings of "Record definition does not exist." (in PTUVIEW_crtvw.log). After digging into this, it appears the "Checking for Invalid Views on Microsoft" step (aka dddinvws.sqr) incorrectly prefixed the Record objects with "PS_" (which is normal on the actual views in the database, but not on the Record object names in App Designer). This issue did not happen in our Demo PeopleTools