We once were doing migration for a project but got stuck when app designer wouldn't copy one of the objects in the project to target instance and kept throwing below error:
Object not copied, parent definition does not exist in target database (62,33)
The error was associated with one AE SQL step and we spend quite some time scratching our head over this. Finally we discovered that we forgot to include the parent section of the SQL Step of the App Engine in the project. In other words, we were trying to migrate a child object without it's parent object.
Well, it doesn't sound convincing right ? because we very often migrate child objects without their parent objects. But in our case it didn't work because the child object (SQL or PeopleCode) was added newly.
Let's try to understand it in a different way. Consider we have an app engine which contains Sections and Steps and this is how they are related.
App Engine - Section(s) - Step(s)
Consider that we have added a new step under a section so if we have to migrate one of the Steps (PeopleCode or SQL) then we must also take along the corresponding parent Section. If you have included the child object but not it's parent then app designer will throw an error (Shown in the first para). To resolve this, include the respective parent section.
