Builder configurations should be set in Visual Studio prior to attempting a build on any application. You should check whether build configurations from EAE 3.3 is migrated. Builder configurations are explained in more detail in the Agile Business Suite Installation and Configuration Guide.
To view the global options for Builder, go to Tools > Options > System Modeler > Builder.
The builder configurations correspond to System View Options in EAE Developer 3.3. The two are quite similar although the mapping of properties to elements is different in Agile Business Suite builder, thereby reflecting the changes to the model in System Modeler.
In AB Suite, there is no separate hierarchy of system elements to which properties are attached. Instead, configuration properties are directly associated with elements in the Class View and other windows in Visual Studio.
Notes:
If the package name is not specified for a deployable folder in configuration, Builder automatically generates unique package names for each deployable folder.
If you provide two deployable folders with the same package name, the build fails.
Alternate Names
Since the Model Importer undertakes migration of EAE 3.3 long element names to Agile Business Suite element names and the old name to the alternate name, Builder uses the old name to avoid having to perform database reorganizations during migration of an existing system from EAE 3.3 to System Modeler. Refer to Name substitutions in the EAE 3.3 to AB Suite Migration Reference Guide for more information.
If no alternate name is specified, Builder attempts to use the full name of the element. If this is invalid, Builder generates a name that does not conflict with any existing legal name. This alternate name might not necessarily be unique for each element. However, non-unique names does not cause problems with the build.