Skip to main content

Migration Package - Widget

Widgets can only be migrated from the system level and created at the system level.   Widgets can be migrated using two types of migration packages: Widget Migration Package Type - to migrate individ

Updated over 2 weeks ago

Widgets can only be migrated from the system level and created at the system level. Widgets can be migrated using two types of migration packages:

  • Widget Migration Package Type - to migrate individual widgets

    migration_package_widget.png

The selected Widget will be migrated, along with the reports (if a prerequisite report has prerequisites, these will be included as well), the User Report Type for all included reports and any referenced User Tables by the reports. There will be no prompting for User Report IDs when selecting this package type.

Exporting of the object - follows the same steps as all migration package types and the object is always exported as a file.

Importing of the object - follows the steps outlined in the "For Dashboard Layout, User Report (include Preq and Type), User Table and Widget migration package types" section.

Things to Note

  • Equus Standard widgets (ones that have been delivered by Equus and have a SYSTEM_CODE starting with “EQ”) cannot be migrated. These do not appear in the Widget drop down list.

  • Landing Experience widgets are not included in this migration package type.

  • Prior to using the Widget Migration Package Type, check the system release versions of both sites. Currently, there is no backward compatibility with Widget Migration Packages created in v21.1 or earlier. Users will need to export the package from a system on v21.2 to migrate the package into a system on v21.2 or later.

  • Information not copied - see User Report (include Prereq and Type) and User Table migration package types.

Did this answer your question?