Forum

There’s really not an option to limit the effect of the build to specific records out of the migration set in Phire.  The closest thing would be to select to “Build Script” option (instead of “Build Script and Execute”) and let it just generate the script.  Then download it from the build history, edit it to remove unwanted records and execute it manually.

Or, just decline the build options altogether, and build manually after the migration is complete.

Remember also, that the Project Build in Phire is the same operation that you perform using Application Designer.  That feature compares the record definitions to the database object to determine what, if any, change needs to be implemented.  So if a record has not changed – that is, no fields were add/removed/changed – then the record will not be altered during the operation.  To do this, be sure that the build setting “Alter even if no changes” is left unchecked.

Have you wondered why PeopleSoft places limitation on which objects can be exported to file? Ever since the feature to export an entire application designer project to file was introduced, there has been no support for Roles, Trees, and Message Catalog. Why? This does not make any sense since these are pretty simple objects that are stored in only few database tables. I asked one of the ex-PeopleTools developer and he could not provide a satisfactory answer. All I can think of is that support for these objects didn’t make the development deadline initially and no one has bothered to go back to fix it.

Anyways, I would appreciate any input on this since this has been bothering me for years.