Syniti Migrate

Deployment Reports

Topics related to this section:

This page contains the following sections:

Prerequisite to Displaying Deployment Reports

These reports are built within the Migrate Mappings section of Migration. They are maintained by developers for use in migration testing runs. Unlike the Migration reports, these reports are filtered by the Deployments involved in the Release.

Security Access -

  • Users who view these reports must first be setup within configuration to have access to view Migration Reports or the reports are not displayed.  This section of Syniti Migrate is generally not granted access to the validation users they have access for specific Deployments.  However, if Deployments are not necessary, then they may be setup for Migration Reports.  Refer to section  Administer > Security > User Management for further details.

  • User who view these reports must first be assigned to Deployments within section Administer > Security > User Deployment. Once one or more deployments are set to active for the user, they may view the list of reports that contain records for these deployments.

  • Within each report details stored in Mappings, a level of sensitive data security may be set at report level. These reports are only visible to the list of users assigned withing the report details page in Mappings. Users who do not have access do not see the report in Migration Reports page. Refer to section Migrate > Mappings > Maintain Target Reports for details of this process.

Working with Deployment Reports

View the following page by navigating to Validate > Deployment Reports from the Syniti Migrate Homepage. Deployment Reports are grouped by Release / Deployment, Subject Area/Datasets, and Types of reports. This type of reporting refers to a more specific level of filtering the data. If the data should be validated by users of different company codes, or countries, it may be advisable for some data to be split into Deployments to allow only the data of that user's deployment to be available for review.

Syniti Migrate supports configurable Environments for projects that require multiple active environments. The ability to separate the MOCK LOAD environment from the DEVELOPMENT environment in order to better support Mock Loads and reporting. As can be seen in the image below, this set of Deployment Reports are set to pull from the DEV Environment. Double - click on the tab label for the Environment to open the Environment Selection window and select the Environment. Once complete, click on Save icon or Cancel icon to exit.

Refer to section Administer > Environments for more details of this process.


NOTEIf a report contains zero rows, then it does not display under the Deployment Reports lists. Every report displays under the Migration Reports (that are set to Publish). To keep the quantity of reporting to a reasonable level, these Deployment Reports only display when there are records in a report with Deployment field values. Once the report quantity goes to zero for a Deployment, the report remains in the list as users want to know that there are no longer records to review.

Reports: Deployment Reports

Click the icon to display a list of reports for that type.

The list defaults as sorted by Report Name, however, any of the columns may be the primary sort.

Reports: Deployment Report List

The Deployment Reports listing page provides the following columns:




Name of the Deployment Report.


Sequence of the Reports. Value increases by factor of 10 for each new entry.


The Report Type categorizes each report and setup for flagging in the All Errors report for errors produced .


The detailed description of the report.

Record Count History

These are spark lines that show the progression of counts for the report in a graph. See section below for spark lines for details.

Last Run

Date this report was run last.


Count of records processed successfully.


The quantity of records that will default as output to prevent excessively large reports.

NOTEDefault value of 1000 at time of save may be changed after saving.


Check Box to show if report is using a random sample of data within the output of this report. This field works with Limit field.

NOTEThe check box is selected within Edit Details.

Security Provides icon to indicate that this report contains sensitive data that only a list of users may view.


This column contains four icons (History, Refresh, View, and Download). Each icon will produce the outcome indicated in their name

The last column provides options for the user such as displaying history, refreshing the report, viewing the report, or download to local drive. See the details for these icons below:





The History icon will show a grid of history for each run of the report with count and date.


The View icon will display the report on page.


The Download icon will save the current report to the user's local drive. See Note below

NOTEReports may only be refreshed by the migration team and not as part of this validation process. Therefore, the Refresh Icon is hidden for this page.

Details Relevant to Deployment Reports list page

Only the reports containing records will provide View and Download icons Active. The Record Count History column will provide a Sparkline of the counts for each report.

Deployment Reports: Sparklines

The Sparklines are built from the history of runs for the report. As shown in the image below, the report history date, and record counts are stored within the History icon of the Options column. The Sparkline will build as the report is run to build the history and if there is no sparkline, then it means that the report has not been run multiple times to build one.

Deployment Reports: Report History display

Edit Deployment Report Details

Depending upon the user's access within Migration application, they may have access to maintain certain fields of the Deployment Report Details page. A click on the Edit  icon will provide the page and certain fields may have access for changes.

Deployment Reports: Edit Report Details

As can be viewed in the image, most of the fields are Display ONLY. However, the user may alter the values for fields - Limit and Random Sample to provide the list that they need from the report.

NOTEFields Business Impact and Recommendation are filled in by the developer. If there are no values in these fields, they will be hidden from validation to reduce clutter on the page.

When finished with edits, click the Save  icon to complete.

Reporting Features for filtering, grouping, and other report functions on page

Once the user decides to view the report, they can use on page filters and grouping to pin point their results.

Refer to section Migrate > Reporting Features for more details of this process.