Importing application metadata

Before any application metadata can be imported, it must first be exported into an XML file. This must be a file that was previously exported using any version of the App Metadata Transport utility.
Note: You can also import metadata using a Command Line Interface (CLI). See Running App Metadata Transport from a CLI.
  1. Open the App Metadata Transport utility (either the form version or the stand-alone version).
  2. On the Action page, select Import metadata from an XML file to a target database, and then click Next.
  3. On the Source page, provide this information:
    Import File Name

    If you know the name of the file, you can type it into this field. Otherwise, perform one of these actions (depending on which version of the utility you are using):

    • In the web client, you can click Upload, which launches the Import Binary Data From File dialog box. Then, either drag-and-drop the XML file from its location on your local computer; or you can click Select File and use the Windows Open dialog box to navigate to and select the XML file.
      Note: Your XML file must have the .XML file extension, or the utility cannot upload it.
    Convert to local Access As
    To convert the Access As identifier of the imported components to be the Access As value of the target environment, select this check box.
    Note: If the IDO project of the IDO to be imported has an Access As value different from the environment in which you are currently working, you cannot convert the Access As value of that IDO collection.
  4. Click Next.
  5. (Stand-alone version only) On the Target tab, select the Target Configuration.
    Note: This page is not available in the form version.
  6. Click Next.
  7. For each of the next series of pages, select the metadata to import, and then click Next.
    Note: For most tabs, you can select none, all, or selected items. Be aware that, if no metadata was exported for any given metadata type in this table, then that page does not display for import operations.
    Page Affected data
    IDOs Multiple database tables, such as ido.Collections, ido.Tables, ido.Methods, and others

    Even though multiple tables are affected, the IDO is imported as a single unit, for example, the ido.Collections record and all its children.

    Property Classes Only metadata in the ido.PropertyClasses tables
    IDO Assemblies Only metadata in the ido.CustomAssembly tables
    Event Triggers Application event trigger metadata
    Event Handlers Application event handler metadata
    Event Global Constants Application event global constant metadata
    Replication Document Elements Metadata for all replication document elements
    Replication Document Attributes Metadata for all replication document attributes
    Replication Document Inbounds Metadata for all replication documents used as inbound documents
    Replication Document Outbounds Metadata for all replication documents used as outbound documents
    Predefined DataViews Metadata for Predefined DataViews, DataView Layouts, and associated DataView Setup information
    Form Extensions Metadata for custom form extensions
  8. Click Next.
  9. On the Summary page, verify the actions to be performed.
  10. Click Finish.
The App Metadata Transport utility imports the metadata from the uploaded XML file and converts it to the appropriate metadata in the application database.
Related topics