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:

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

Export whole contents of a package in SQL:

Select desired DBMS product for SQL dialect:

Export whole contents of a package in CSV format:

Select desired DBMS product for CSV export:

Clone package and its contents:

Cloning can be done with Clone or Deep clone option:

Delete package and its contents:

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

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:

Commit and deploy the deletion across all Runtime environments where the package was previously deployed.
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.

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

EXAMPLE

DV_TAXI_LOCATION_CLONE_20210407102815

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