ERP Associates, Inc.

Don't you hate it when you ask for a project to get migrated to Test, and it doesn't work there?  Then you do some research, and it's missing some critical PeopleCode or SQL and the users are getting big ugly errors and questioning the quality of your work.  Okay, maybe it's not always that dramatic, but it is always frustrating.

Here's some of the reasons things don't always get migrated and what you can do:  

1. It’s not in the project. Just because you insert the App Engine doesn’t mean you inserted the App Engine sections. Just because you inserted a record definitition doesn’t mean the SQL/Record PeopleCode got inserted. Just because you inserted a page doesn’t mean the Page Pcode got inserted, and just because you inserted a component doesn’t mean the (almost useless) menu that refers to it got inserted, or the pages it refers to, or the component PeopleCode got inserted. Review the “Upgrade Tab” of your project to make sure all of the components are really in your project before you request that migration!  Or better yet -- use the F7 key to insert everything you touch into your project as you work.

2. The upgrade flags weren’t set right. Once again, check the upgrade tab. Make sure the “Upgrade” flag is set for EVERYTHING that you want to migrate. Also, make sure the Action is set to Copy.

3. The object is locked in the target environment. This usually happens in special circumstances (like migrating code back to the development environment when applying patches). I guess it COULD happen if you have change control turned on in your target environment, but I can't think of a reason why you'd do that.

4. It did get migrated, but you don’t have security to see it. Lots of times the security that worked great for you in development won’t work in other environments because frankly nobody uses the ALLPAGES permission list except in DV. Part of the migration request should be a note to your security administrator to set it up in security after the migration.

5. The person migrating made a mistake. This happens less than you might think. The actual migration process is pretty much a no-brainer. But mistakes can happen and the person migrating might accidentally unselect an object type, or migrate it to the wrong environment. Usually it’s easy to open the project in the target environment to make sure it exists, then double-click on whatever object you want to check to make sure it’s there. You can do this even if you have read-only app designer access.