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 under the navigation icon (three dots at the upper right corner) when opening a package:

Package Actions_1.png

Export package

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

Package Actions_2.png

Export package SQL

Export whole contents of a package in SQL and select desired DBMS product for SQL dialect:

Package Actions_3.png

Export package CSV

Export whole contents of a package in CSV format and select desired DBMS product for CSV export:

Package Actions_4.png

Clone package

Clone package and its contents:

Package Actions_5.png

Cloning can be done with Clone or Deep clone option:

Package Actions_6.png

Delete package

Delete package and its contents:

Package Actions_7.png

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

Package Actions_8.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.