Documentation

    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

Connect an AI assistant

Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.

The catalog did not load. Refresh the page to try again.

Loading…

How can we help?

{{docApp.searchError}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

 {{docApp.currentResultsSearchText}}  in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown. Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

  • {{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}

    {{resultItem.url}}

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

Upload Assets

You can manually upload multiple assets for specific asset classes from CSV files. This option is provided to allow the insertion of new assets into the Service Manager asset repository. Manual upload is generally used for static data. If you need to schedule the importing of new assets or updates to existing assets from discovery tools, MSSQL, or MySQL databases, you can find more information about the Asset Import utility in the Data Imports Guide.

As an Asset Management Administrator, select Asset Upload from the Asset Management icon in the application navigation bar.

Creating the upload template

You can upload assets of different asset types, but only those that are managed under the same asset class, from a single CSV template. If you need to upload assets for types that are managed under different asset classes, you must create different CSV templates for each asset class grouping.

To create your upload template:

  1. From the dropdown control against which you wish to import the new assets, select the asset class. This enables the option to download the related asset class template.
  2. Select to download the template file.
  3. Populate the template file rows and columns with the attributes for each asset you want to upload. Name and Type are mandatory attributes for each asset you wish to upload, regardless of its type or class.
  4. Click Save.

While other attributes are not mandatory to perform the import, it is good practice to populate the attribute fields to match those that you enabled for each asset type (when you were defining the asset types).

For example, with Used by or Site, should you want the assets to appear as linked to these entities when performing other Service Manager actions (such as logging requests through Intelligent Capture and having the option to choose from a list of assets associated with the user), you should match up the attribute fields.

Used by requires the usedById attribute to be completed. The upload process will automatically verify the user exists and populate the user name field.

Owned by requires the ownedById attribute to be completed. The upload process will automatically verify the user exists and populate the user name field.

Site requires both the site and the siteId attributes to be completed. SiteId refers to the database numerical value, not the display name.

Date attributes are required in the following format: yyyy-mm-dd hh:mm:ss

The Country field requires the ISO Alpha 2 codes as per the listing in this Wikipedia article.

The fields in the CSV file are mapped on the assets database table.

To find which values and types need to be populated in the fields:

  1. Navigate to Home > Applications > Service Manager > Entity Viewer
  2. Select Database Schema Viewer and navigate to the h_cmdb_assets table.

Validation

Against each asset class, you can configure which fields for that given asset class you wish to perform data validation. This is done before uploading the assets from the CSV file into the Service Manager asset repository.

As each customer may be using different unique identifiers, each customer can select from the available fields for each asset class, against which to perform the validation to ensure an asset does not already exist, and therefore avoid the creation of duplicate entries.

  1. Click Validation.
  2. Select one, multiple, or all of the available fields to perform the validation checks against.
  3. Click Save.

Note that data validation, and the number of checks required, will extend the upload time for the asset import.

Select CSV file to upload

To initiate the asset upload, select the CSV file you wish to use. Selecting the file will populate an inline table. It will run some basic client-side validation checks and report any issues found. Rows with issues will be shown with alert badges and amber highlighting. The table allows you to filter to show bad rows and you can edit row data inline to fix any bad data.

When you are ready to import you can import filtered, selected rows or all rows. When the import begins it will process 1 row at a time. If a row fails import it will be highlighted and the next row will be processed. At the end of the import run you can see:

  • The number of records processed
  • The number of records successfully uploaded
  • The records that failed to upload

If during the import process, specific rows of asset data are not able to be imported, this will be detailed below, including:

  • Which rows failed
  • The reason for the failures

You can choose to fix failed row data if you wish and try importing just those rows again.

  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document