Application fields available for bulk data import

Modified on Thu, 22 Jan at 12:58 PM

TABLE OF CONTENTS

Overview
Available Application Fields
Bulk Importing New Applications
- Import Steps
Further Support

Overview

In some projects, information about certain applications (such as web or custom in-house apps) may not be captured by the main inventory source integrated with ManagementStudio. In these cases, project administrators can manually import application data using an Excel source. This guide outlines the available application fields for import and explains the bulk import process.

For a full overview of data imports, see the Data Importer article.

Available Application Fields

The following table lists the fields available for bulk importing applications into ManagementStudio:

Field Name	Description	Required?
`App ID`	Unique reference generated by ManagementStudio when an application is imported. Creating a new application: Leave blank—ManagementStudio will assign an ID during import. Updating an existing application:Required—ensures incoming data maps to the correct record. To locate App IDs: Go to the Applications module. Click Select All. Expand the Copy dropdown and choose Export to Excel All.	Yes (when updating only)
`App Vendor`	Name of the application's vendor (e.g., Symantec).	Yes (for new imports)
`App Name`	Application name (e.g., Excel).	Yes (for new imports)
`App Version`	Application version (e.g., 15.0).	Yes (for new imports)
`Start Date`	Deployment unit start date.	No
`Process Status`	The internal process status for the application's workflow stage.	No
`Process`	The current process stage (e.g., if the application is in UAT, set to `5. UAT`). This changes the status from the default `1. Identified`.	No
`Sub Process`	The current sub-process. Should be used in combination with `Process`. Example: for process `5. UAT`, set sub-process to `UAT Queue`, `UAT in Progress`, or `On Hold`.	No
`Also Known As`	Alternative names for the application (e.g., Office Word).	No
`Superseded To (AppId)`	App ID for any application that supersedes this one.	No
`Superseded To (Name)`	App name for any application that supersedes this one.	No
`Is Archived`	Marks applications as archived if rationalised. Archived apps are removed from the primary application view. Uses a checkbox.	No
`Priority`	Application priority (`Low`, `Medium`, `High`). Useful for indicating importance in workflows such as packaging.	No
`Package Type`	Packaging or delivery format (e.g., App-V, MSI, Citrix).	No
`Assigned To`	Person responsible for the application at its current workflow stage.	No
`Localisation`	Language or region for the application (e.g., United Kingdom).	No
`Date Required`	Date when the application is required to be ready for production.	No
`Description`	Short summary of the application (e.g., "Word, part of the Microsoft Office suite").	No
`Complexity`	Application packaging complexity (`Basic`, `Normal`, `Medium`, `Complex`). Used to indicate required resources.	No
`CustomProperty (1-10)`	User-defined fields to capture additional application data.	No
`CustomList (1-5)`	Internal custom list fields.	No
`CustomDate (1-4)`	Internal custom date fields.	No
`CustomInt (1 & 2)`	Custom integer fields for additional numeric data.	No
`CustomFlag (1-3)`	Checkbox fields; use `Yes/No`, `True/False`, or `1/0`.	No
`Email`	Primary contact email address (e.g., application owner email).	No
`CoreApp`	Indicates core applications that should be deployed to all users (set using the `Is Core App` field).	No
`Architecture`	Application architecture (e.g., x86, 64-bit).	No

Bulk Importing New Applications

Before starting, ensure your application data is prepared in an Excel file using the field names above.

Import Steps

Click Import Data.
Select Applications as the import area.

Browse and select your prepared Excel file.

Click Try to Auto Match to let ManagementStudio map columns automatically when there are matching field names in your file.
Match your import file fields against the ManagementStudio Fields.
Tick Create if not found if importing new applications. If updating, ensure Update if found is ticked.
Check Move to Process and select the relevant process stage for these applications.
Click Preview Import to review, then select Import Data to proceed.

On the confirmation screen, click Import.
After import, an import report log will display results. Click OK to complete.

Return to the Applications module—newly imported applications will appear in the grid.

Further Support

For additional assistance, visit the ManagementStudio Service Desk for knowledge base articles or to submit a support ticket.