E-AD: Get "Class Record: assumed property XXXX is not a valid field name. (2,274)" after Record Definitions being Migrated to Multiple Databases via AppDesigner
(Doc ID 1272190.1)
Last updated on FEBRUARY 03, 2019
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.40 to 8.51 [Release 8.4]
Information in this document applies to any platform.
*** Last revision 02-Apr-2015 ***
In PeopleTools 8.40-8.51, if a database Record and a PeopleCode routine that accesses that record are modified and then migrated together via App Designer from one PeopleSoft database to several other PeopleSoft databases, in the new environment the modified record definition often is not being picked up by the modified code, so that new code tries to operate on old record, usually triggering mismatch errors.
Clearing cache of the sever domain where the code runs (app server or batch server) eliminates the error.
The issue forces developers to always clean server cache in target systems after migrating modified programs and metadata, it is an inconvenience and slows down the development cycle.
- Either create new or take an existing AE program with a PeopleCode that accesses a database Record, make sure it works.
- Add a new field to the Record and save, and change the AE PeopleCode to reference the new field.
- Test the modified AE program accessing the modified reord in that environment, make sure it works.
- Migrate the modified AE and the Record into several other environments via App Designer, rebuild Record in the target environments.
- Run the AE program in the new environments, observe the "...not a valid field name" error.
- Clear the Process Scheduler server cache in the target environment where the AE program failed.
- Rerun the AE program in that new environment, observe that now it runs to success.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!