Object Specifications

Object Specification Syntax

<Object type>: ALL[(<Version number>)] | <Object name>[(<Version number>)] {<Object name>[(<Version number>)]}

Existing Object Types

Type	Description
CL:	If Classes must be exported or imported.
DI:	If dictionaries must be exported or imported.
EI:	if external interfaces must be exported or imported.
FD:	If file definitions must be exported or imported.
FO:	If forms must be exported or imported.
GD:	If global definitions must be exported or imported.
GR:	If global routines must be exported or imported.
IM:	If imagelists must be exported or imported.
IN:	If indexes must be exported or imported.
RA:	If REST API web services must be exported or imported.
RE:	If reports must be exported or imported.
SC:	If scripts must be exported or imported.
SP:	If stored procedures must be exported or imported.
SQ:	If sequences must be exported or imported.
TA:	If tables must be exported or imported.
VI:	If views must be exported or imported.
WS:	If web services must be exported or imported.

Object Specifications

Specification	Description
ALL	Indicates that all objects of the concerned object type must be exported or imported.
<Object name>	Name of the object to be exported or imported.
(<Version number>)	Version number that must be assigned to the imported object included in parenthesis. E.g. (3.1.4). Note: This option does not apply if the parameter file is used for exports.


Multiple objects of the same type can be specified by delimiting the object specifications by single spaces. All specifications of the same object type must be specified on a single line.

Version numbering on import

To import objects under a new version number, the new version number must be specified between parentheses directly after the concerned object specification. The new version number must be a higher version than the previous one if its a main revision (1.2, 1.5, etc.).

Also importing under a branch is allowed but the following rules apply:

The main revision (first two numbers) must exist.
The branch nodes may or may not exist (1.2.1, 1.3.2, etc.). When not, the import creates the branch node.
The revision must be the highest revision in an existing branch.
The previous revision in the branch may NOT be locked.
When specifying an invalid revision the object is NOT loaded.

Example:

When having revisions
	1.4
	1.3
	1.2
After importing revision 1.3.1.4
	1.4
	1.3.1.4 <- Loaded revision
	1.3.1 <- Automatically created branch node
	1.3
	1.2