Export Development Objects

You can export application definitions from the Repository to an XML file. This is useful when you need to share objects with a colleague, or backup a set of objects.

Note the following:

  • It is not possible to append export data to a file created with the data copy facility.
  • When appending data to an existing export file, the Repository version attributes must match exactly.

To export application definitions:

  • To export a selection of various objects, such as component, entities, and global objects:
    1. In the Uniface IDE, choose Main Menu ( ≡ )>Export to open the Export form.
    2. Use a retrieve profile to select the objects to export. You can do any of the following:
      • Click Browse to browse for and select an object.
      • Specify a GOLD ; separated list of component names; for example, ORDER_ENTRY;ORDER_LIST
      • Enter a retrieve profile using GOLD * ; for example ORDER_*
      • Click Select All to enter the wildcard GOLD * in every field, thereby exporting the entire Repository
    3. Enter a file name or choose an existing file, and select Append if you want to add to an existing file.
    4. Click Export to export the selected definitions.

  • To export objects in a project, open the project in the Uniface IDE, click Actions and choose the desired Export option:

    • Export to XML—export only the project itself and the reference objects it holds.
    • Export full Project to XML—In addition to the project and its references, export the referenced objects. If it contains another project, the referenced project is included, but not its main development objects.
  • To export an individual main development object, open it in the Uniface IDE and choose Actions >Export to XML....
  • In ProcScript, use the $ude ("export") function. This is useful if you want to create your own customized export utility. For more information, see $ude ("export") .

Uniface exports data as well-formed, well-defined XML in which objects that have aggregation relationships are nested. The export facility takes referential integrity constraints into account, ensuring that all the data applicable to an object definition is correctly exported.

Once exported, you can import the file into a compatible Repository.

Related Topics