Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WDESIGNER and version 24.0

To exchange Designer content between systems or namespaces, or simply to create a copy of something, you can export and import the contents of the explorer tree. However, import and export are not equally allowed for all elements. The table below lists the available options for each element:


NamespaceFolderService
Export(error)(tick)(tick)
Import(tick)(tick)(error)

Version Considerations

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameversion_considerations
PageWithExcerptINTERNAL:_designer_excerpts

Limitations

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameimport_limitations
PageWithExcerptINTERNAL:_designer_excerpts

Exporting Explorer Content

If you want to export an element, for example to create a backup copy of your model, select Export from the context menu.

On exporting from a Folder or Service, you have the choice whether or not to include the libraries used in the export.
By default libraries are included in an export.

Click Export to confirm your choice and start the exporting process.

During the export a message Generating file... is displayed.

A toast message also confirms a successful export.

Importing Explorer Content

If you want to import an element, for example to transfer a backup copy to another namespace, select Import from the context menu.

A pop-up Import opens.

Click Browse to select the file you want to import.

The name of the selected file is displayed. To change your selection, click Change File.

Start the import by clicking the Import button.

A toast message confirms a successful import.

Export files may contain necessary libraries. If you import an export file containing libraries, you will be notified by a pop-up notice.

Two different notes are possible:

  • Libraries imported successfully: The listed library versions have not already been available in the namespace and have been imported successfully.
  • Libraries already present in the namespace: The library version to be imported is already present in the namespace, and is therefore ignored. This applies to libraries of the same version, no matter if the imported library has the same or a different timestamp.

    Info

    Please check the imported service for functionality as the existing library will be assigned to the new service.

The imported element is displayed in the tree.
Panel
titleOn this Page:
Table of Contents
Panel
titleRelated Pages:

Otp
Floatingfalse
maxHLevel2

rp