User Reports can be migrated from the system level or company level. Using this migration package type, the migration of all prerequisite reports (if a prerequisite report has prerequisites, those will be included as well) and the User Report Type for all included reports will be included. There will be no prompting for User Report Type IDs when selecting this package type. Also included in the package type are any User Tables referenced by the report(s).
When company-level reports are migrated using this package type, they will remain at the company level when migrated (assuming the same company exists in the destination system).
Similar to the User Report migration package type, it is not possible to create a migration package for an Equus standard User Reports (ones that have been delivered by Equus and have an Equus System Code).
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 Prereq and Type), User Table and Widget migration package types" section.
User Report Information Not Copied
Report "Favorite"
Used for Widget (will not appear in the portal reports lists) - This is only available for company-level reports, and therefore will not be copied over to the target system as all user reports are created at the system level.
Account Sums
Custom Fields - If the field exists and is configured, it will be included. If not, the report will show an error/missing field
Views (custom and standard) - If these exist in the destination system, the User Reports and User Report Types can reference these. However, the import will fail if the View does not exist in the destination system.
The data on the User Table is not included
See Things to Note section for User Table migration package types
Things to Note
Generated SQL is copied with the User Report only if the User Report's SQL exists in the "source". Running a user report will generate the SQL. It is strongly recommended that user reports are tested by running it prior to migration.