Breadcrumbs

Package Actions

Package Actions enables different package export options, possibility to clone a package or delete a package.

See also:

Usage

Package actions can be found inside each package:

image-20230207-113801.png

Export package

Package can be exported in JSON-format. There are multiple options for package export:

image-20230207-113805.png

Export package SQL

Export whole contents of a package in SQL:

image-20230207-113814.png

Select desired DBMS product for SQL dialect:

image-20230207-113818.png

Export package CSV

Export whole contents of a package in CSV format:

export_csv_700.png

Select desired DBMS product for CSV export:

image-20230207-113823.png

Clone package

Clone package and its contents:

clone_package.png

Cloning can be done with Clone or Deep clone option:

clone_package_options.png

Delete package

Delete package and its contents:

delete_package.png

Deletion will prompt confirmation on whether package will be deleted or not:

package_delete.png

When you delete a package:

  • All entities contained within the package are also deleted.

  • Both the package and its entities are soft-deleted, meaning they are not permanently removed and can still be viewed.

  • Entity loads are permanently deleted.

  • To view soft-deleted items, enable the Show deleted toggle in the package or entity lists.

After deleting a package:

  1. Commit and deploy the deletion across all Runtime environments where the package was previously deployed.

  2. This step is critical to ensure that:

    • ADE metadata is updated consistently.

    • The target database remains synchronized with the current state of the package configuration.

Failing to deploy the deletion may result in errors and inconsistencies.

Notes

Cloned package is named like the original one but with a suffix "_CLONE_TIMESTAMP" e.g.

DV_TAXI_LOCATION_CLONE_20210407102815

With deep clone, entity names, load names and entity mappings get a similar suffix.