Skip to content

DTP reports

From the contributor cockpit, the following reports can be launched from the action panel by clicking on the DTP item, but only when executed from lowest level element and if the execution is standard (i.e., context independent).

Note:

  • these reports are not accessible from the Detail summary tab.
  • In the audit, you can review anomalies, but only the first 10 are displayed.

Checking rules report

The DTP's checking rules report can be run from the contributor cockpit. In the cockpit, details of the dataset/typology paid on which the checking rules have been run are shown at the end of the activity. A list of the checking rules run by the DTP can be exported for every record, in XLSX format. The generated file name will have the following structure:

REGOLEDICONTROLLO______.XLSX

Warnings report

From the contributor cockpit, it is possible to run the anomaly report from the Data Transformation Package task by clicking on the DTP button in the action bar.

This report shows errors found in DTP operations. Specifically, if a task ends with anomalies, it displays the list of operations that caused those anomalies during the last run, along with the number of anomalous records found.

When an operation with anomalies has performed a check on a dataset, it is possible to download an XLSX file containing details of the dataset rows with anomalies.

The table columns show the following information:

  • the DTP that generated the error
  • the activity
  • the Target dataset
  • the target Type
  • the n-tuple of LOOP values belonging to the activity iteration
  • information on the checking operation that found the error
  • the operation type
  • the n-tuple of LOOP values belonging to the operation iteration
  • the user that ran the data processing
  • the data processing run time

The XLSX file shows all the errors found since all the DTPs present in the task workflow were last run.

In the rows above the table with the anomalous values of the operation, the following information is displayed:

  • the first row of the file contains the code and description of the operation
  • if the operation is part of an activity that has an associated LOOP, the n-tuple of the activity's LOOP iteration values is shown, followed by the n-tuple of the operation's LOOP iteration values if it has an associated LOOP.
  • the error message defined on the operation page.

The table with all anomalous data is shown below.