Skip to main content

Data imports

Data imports enable you to import data into SaaS that is not automatically captured by your other discovery sources. Once imported, this data is consolidated into indicators, charts, and tables on the SaaS pages. You can use Data imports to:

  • Update multiple subscriptions in a single flow. Add or modify any of the standard, editable subscription fields in SaaS.
  • Update multiple users in a single flow. Add or modify any of the standard, editable user fields in SaaS, and any custom fields you have configured for users.
  • Add user and user activity data for an application. Add or update data for applications that are not supported by the SaaS connectors, or applications captured by a connector that does not return API data on users and activities.

Below lists the SaaS applications based on their level of integration support provided with the data imports feature:

Fully supported applications: Adobe Workfront, Akamai, Apptio, Asana, Autodesk, CyberArk Identity, Domo, Fastly, Figma, Github, HubSpot, Kaltura, Lucidchart, Miro, Namely, OneLogin, Oracle Fusion, PingOne, Poll Everywhere, PractiTest, Smartsheet, Webex, Workday, and Workiva.

Partially supported applications: Jamf PRO

Import subscription data​

note

This feature is currently in beta and available only in select tenants. To request access, please contact your Flexera representative.

When uploading data for subscriptions in Data imports, keep in mind the following:

  • The Subscription name and Subscription ID values are not validated during the import setup. To ensure successful mapping, do not change these values unless you are updating the Subscription name for a manually-added subscription.
  • If a subscription does not have existing values for Billing period and Metric, these fields must be added to the CSV and mapped in the Mapping step when you create the import. If a subscription already has values for Billing period and Metric, these fields do not need to be mapped.
  • Purchase date, Cost per unit, and Currency are interdependent. All three values must be provided or the record will fail to import.
  • For Currency, you must enter a currency that exists in your Snow Atlas tenant or the record will fail to import. For more information on currency management in Snow Atlas, see Currency settings.
  • Expiration date must use the format yyyy-mm-ddT00:00:00:00Z. It cannot be assigned a null value or the record will fail to import.

You can upload CSV files in Data imports to update information for your subscriptions in SaaS. This enables you to modify or add fields for multiple subscriptions at once, rather than edit them individually. In Data imports, you can update any of the editable fields for your subscriptions. For more information on the supported fields, see Edit subscription: Reference.

Before you create an import, you should generate a CSV template. This template lists all the editable fields that can be modified for the subscriptions you choose to update. For information on generating templates, see Generate import templates. Once you have modified or added fields in a CSV template, upload the CSV file in Data imports. For more information, see Create data imports.

When you create the import configuration, the CSV file is processed and saved in the system. Data from the import is displayed in SaaS when the Data Update Job completes, or when you manually select Update data at the bottom of a page in SaaS.

Import user data​

You can upload CSV files in Data imports to update information for your users in SaaS. This enables you to modify or add fields for multiple users at once. You can add or update any of the editable fields for users, including custom fields that you have configured for users. For optimal performance, limit CSV files to 1000,000 users.

Before you create an import, you should generate a CSV template. This template lists all the editable fields that can be modified for the users you choose to update. For information on generating templates, see Generate import templates. Once you have modified or added fields in a CSV template, upload the CSV file in Data imports. For more information, see Create data imports.

note

The ID and Name columns should not be changed. Changes to these values are not validated during the import setup and may cause imports to fail.

When you create the import configuration, the CSV file is processed and saved in the system. Data from the import is displayed in SaaS when the Data Update Job completes, or when you manually select Update data at the bottom of a page in SaaS.

Import user entities and activities for applications​

You can upload CSV files in Data imports to add information about users and user activities for applications. Each import can have multiple user or activity records pertaining to an application. For data from an Activities import to appear on the SaaS pages, a corresponding Users import must exist for the same vendor and application, and the user identifiers in Activities must match those in Users. For information on creating data imports for Users and Activities, see Create data imports.

When you create an import configuration, the CSV file is processed and saved in the system. Data from the import is displayed in SaaS when the Data Update Job completes, or when you manually select Update data at the bottom of a page in SaaS. Users and activity data retrieved from an import configuration are represented by the Data import discovery type in SaaS. For information on discovery sources, see SaaS discovery.

You can update the data captured by a Data import by uploading modified or new CSV files for the import configuration, or by creating an API integration. For more information, see Upload additional data and Create API integrations.

API integrations​

note

API integrations are only supported for Users and Activities imports.

API integrations can automate the workflow to update data captured in a Data import. These integrations can be supported by automation scripts you create in your local environment that trigger the API calls required to upload data in a CSV file, and then import that data into SaaS. The basic flow for an API integration is as follows:

  1. Request an upload URL to Azure blob storage from the Snow Atlas API. The response includes a pre-signed, time-sensitive URL to Azure blob storage and a file ID.
  2. Upload a CSV file to Azure blob storage using the pre-signed URL.
  3. Create a task to import the CSV data into SaaS by placing a request to the Snow Atlas API.

For more information on the steps that can be automated with scripting, see Create API integrations.

To create API integrations, you require access to the Snow Atlas APIs. To get access, create an application registration that has the Manage SaaS data import API integrations permission for SaaS Management. Creating an application registration generates client credentials that you can use to obtain an access token for the Snow Atlas APIs. For more information, see Manage application registrations and Authentication with client credentials.