View a remote package summary

You can use the Management of Change (MoC) Package tool (dnapackage) to view a summary of changeset entries added to a package published to the store.

To view a summary of changesets added to a remote package

1. On the desktop, double-click the Windows PowerShell for DNA shortcut.

   Windows PowerShell for DNA opens.

2. Execute the following commands:

   set-silo RealTime

   dnapackage summarize --title <package title> --path <summary path> [--changeset <changeset id> –-type <type>] [--dalfolder <DAL configuration folder> --username <remote username> --password <remote password>]

   Where:

   • --title <package title> is the title of the package.

   • --path <summary path> is the absolute path to which you want to write the changeset summaries.

   • --changeset <changeset id> is the identification number of the specific changeset you want to view.

   • --type <type> describes a valid changeset type (for example, --type display).

     Important: While --changeset and --type are optional, you must either a) include both of them or b) include neither of them.
     
     Note: If a changeset and type are not specified, all changesets in the package will be summarized.

   • --dalfolder <DAL configuration folder> is the DAL configuration folder name on the remote system you are trying to connect to (for example, --dalfolder systemName\control_room).

   • --username <remote username> is the username of the user on the remote system you are trying to connect to.

   • --password <remote password> is the password of the user on the remote system you are trying to connect to.

     Note: The --dalfolder <DAL configuration folder>, --username <remote username>, and --password <remote password> parameters do not need to be included if you are viewing the summary of changesets added to a remote package on the same server as the MOCOrchestrator service. These parameters are mandatory if you are viewing the summary of changesets added to a remote package on any other server that does not have the MOCOrchestrator service. For example, viewing the summary of changesets added to a remote package on the Production MoC zone would require remote DAL configuration to connect to the MOCOrchestrator service.

Examples

The dnapackage summarize command –-title "packageTitle" –-path C:\temp\summary.csv might result in the following output:

Changeset: 10

Displays Affected: 4

Changeset summary written to C:\temp\summary(10)_Display.csv.

Changeset: 12

Tables Affected: 3

Columns Affected: 108

Unique Rows Affected: 107

Changeset summary written to C:\temp\summary(12)_RealTime.csv.

Changeset: 16

Tables Affected: 1

Columns Affected: 4

Unique Rows Affected: 102

Changeset summary written to C:\temp\summary(16)_RealTime.csv.

The dnapackage summarize command –-title "packageTitle" –-path C:\temp\summary.csv –-changeset 12 –-type realtime would result in the following output:

Changeset: 12

Tables Affected: 3

Columns Affected: 108

Unique Rows Affected: 107

Changeset summary written to C:\temp\summary(12)_RealTime.csv.