Imported Data Mapping

FlexNet Manager Suite 2023 R1 (On-Premises)

Data imported through the Flexera One SaaS Management connector is matched to records previously imported through the same connector into FlexNet Manager Suite (where available), or new records are automatically created.

Important: Imports through the Flexera One SaaS Management connector do not update records created from other connectors such as the Salesforce connector, the Microsoft 365 connector, or the Microsoft Office 365 (deprecated) connector. For information about switching connectors and data clean-up, see Deprecating Other Connectors.

The data flow through this connector is one way – some imported data points (such as the available entitlements) are not editable within FlexNet Manager Suite, and must be edited within Flexera One SaaS Management and reimported in the next nightly full inventory import. A link is provided on the property sheet of relevant licenses to help you switch contexts, and you can also activate a button in the navigation bar for switching to Flexera One SaaS Management (see the Integrations tab of the System Settings page). Similarly, deleting a matched data record (such as a license) within FlexNet Manager Suite does not automatically delete the matching data in Flexera One SaaS Management, where the record must also be deleted manually (otherwise the next inventory import simply recreates the matching record to align with the source data).

Tip: As well, deleting a license within Flexera One SaaS Management does not automatically delete the matching license in FlexNet Manager Suite, even after the next import and license compliance calculation. Similarly, deleting an imported application record does not delete the equivalent managed application within Flexera One SaaS Management. To delete a license or managed application originating in Flexera One SaaS Management and mirrored within FlexNet Manager Suite, you must access each of the records separately in the two products, and manually delete each one.

Almost all SaaS products are handled identically in FlexNet Manager Suite, and represented with SaaS User licenses. The one exception is Microsoft Office 365: because a license entitlement here may authorize use either as a SaaS application or as a locally-installed application on a device, these are handled separately and represented as Named User licenses. As a result, the data flows/storage is quite distinct for this case.

Tip: Flexera One SaaS Management allows you to create one Office 365 license that is linked to multiple plans, such as Office 365 (E1) and Office 365 (E4). Because each plan brings with it changed license entitlements, within FlexNet Manager Suite each plan for Office 365 is automatically given a separate license. This may mean that you see two (or more) licenses in FlexNet Manager Suite that link back to the one source license in Flexera One SaaS Management.

The following tables show properties found in the user interface of Flexera One SaaS Management, and track their initial staging within the compliance database of FlexNet Manager Suite (with the database table name shown in the header of each list), and their common property name in the web interface. Fields in the target table are omitted if no related data is imported.

Note: The following ImportedUser table is populated only for Microsoft Office 365 users. These records are linked to existing user properties (ComplianceUser records) when these already exist; or else new user records are created.

Table 1. User data mapping for Office 365 (ImportedUser table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
First name	FirstName (up to 128 characters)	User properties > General tab > First name
Last name	LastName (up to 128 characters)	User properties > General tab > Last name
Email	Email (up to 200 characters)	User properties > Details tab > Email
Hard-coded to 1	MapUsingEmailAddress	Not visible. Attempts to match existing compliance user record by email address.
Unique ID in user properties	ExternalID	Not visible.

Note: The following ImportedAccessingUser table is used for all SaaS products and licenses with the exception of Office 365. (A user of both kinds of licenses appears separately in each of these imports.) Be aware that, for these SaaS products, there may be accessing users who come from outside your enterprise (for example, if you allow consultants or customers to access your Salesforce pages).

Table 2. User data mapping for other SaaS applications (ImportedAccessingUser table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
Email	UserName (up to 200 characters)	License properties > Consumption tab > User External users show their email address. Users from within your enterprise (who have been matched on their email addresses) display their full name as a hyperlink to their user properties.
Email	SAMAccountName (up to 64 characters)	Not visible in user properties.
Derived from the Email value	DomainName (up to 100 characters)	License properties > Consumption tab > Domain name
Internal ID	ExternalAccessingUserID	Not visible. Used for record matching.

Table 3. Access data mapping (ImportedClientAccessEvidence table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
Internal ID app.id (not visible)	ExternalAccessEvidenceID	Not visible. Used for record matching.
Managed Applications > APPLICATION	ProductName	Application properties > General tab > Product
Managed Applications > VENDOR	Publisher	Application properties > General tab > Publisher

Table 4. Access counting (ImportedClientAccessedAccessOccurrence table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
Internal ID AppUsr.id (not visible)	ImportedClientAccessed AccessEvidenceID	Not visible. A separate record is created for each pairing of a user and application. For example, if UserA accessed two SaaS applications, there are two records.
Hard-coded to 1 for each date	AccessCount	License properties > Consumption tab > Last used count
None. Uses the date when data is imported from Flexera One SaaS Management to FlexNet Manager Suite.	InventoryDate	Inventory device properties > General tab > Last inventory date
Does not use the Effective Date from the License Details tab of the license properties.	LicenseDate	Not separately visible. Uses the inventory date in a different format.
Last Activity listed for this user in the Users tab of the application properties.	AccessDate	Application properties > Devices tab > Last used date

Table 5. Evidence to application links (ImportedSoftwareTitleAccessEvidence table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
Internal ID app.id (not visible)	ExternalSoftwareTitleID	Not visible. Foreign key to the ImportedSoftwareTitle table, identifies an imported application
Internal ID app.id (not visible) (same value)	ExternalClientAccess EvidenceID	Not visible. Foreign key to the ImportedClientAccessEvidence table, identifies an imported record of user access

Note: The following mapping into the ImportedComputer table creates (if it does not already exist) a dummy device record (needed within FlexNet Manager Suite, but not available in Flexera One SaaS Management). Only a single dummy computer record (for each connector) is required.

Table 6. Computer data mapping (ImportedComputer table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
None. Uses ComplianceConnectionID.	ExternalID	Not visible –
Hard-coded to "Flexera SaaS Manager"	ComputerName	Inventory device properties > General tab > Name
Hard-coded to "flexera.com"	Domain	Inventory device properties > General tab > Domain name
Hard-coded to "Flexera SaaS Manager " with the numeric value of the ComplianceConnectionID appended	SerialNo	Inventory device properties > General tab > Serial number
Hard-coded to "Flexera SaaS Manager"	InventoryAgent	Inventory device properties > General tab > Last inventory source
Hard-coded "False"	UntrustedSerialNo	Not visible
Hard-coded "False"	IsRemoteACLDevice	Not visible
Hard-coded "False"	IsDuplicate	Not visible
Hard-coded "False"	IgnoredDueToLicense	Not visible

Note: The following mapping into the ImportedSoftwareLicense table updates or creates either of two kinds of license, matching those in Flexera One SaaS Management:

• Named User licenses for Microsoft Office 365
• SaaS User licenses for any other imported SaaS applications.

Table 7. License data mapping (ImportedSoftwareLicense table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
Not visible termId	ExternalLicenseID	Not visible
License properties > License Name combined with the Name field (adjacent to the License Type control). For example: License name = G Suite Name = Monthly/User	LicenseName Example value imported is: G Suite - Monthly/User	License properties > Identification tab> Name
Managed Applications > Vendor for most applications (when creating SaaS User licenses); or for Named User licenses, value take from SKU is Microsoft Corporation.	PublisherName	License properties > Identification tab> Publisher
# of Items Allowed as a number	EntitlementCount	License properties > Compliance tab > Extra entitlements (see also next item)
# of Items Allowed shows Unlimited	UnlimitedConsumption	License properties > Compliance tab > Entitlements are: Unlimited (see also previous item)
Set to 13 (the ID for the Named User license type)	SoftwareLicenseTypeID	License properties > Identification tab> License type (displays as Named User)
License properties > Ending Date (or, in the list of Application Licenses, the END DATE)	ExpiryDate	License properties > Identification tab> Expiry date
The prefix FLX-O365- followed by the internal termSKU value (not visible)	PartNo	License properties > Purchases tab > Part no./SKU
Hard-coded to true	IsSubscription	License properties > Identification tab> Purchased as displays Subscription
Not visible Id	SaasManagerLicenseID	Not visible – used for creating the hyperlink from the license in FlexNet Manager Suite back to the matching license in Flexera One SaaS Management.

Note: The following mapping into the ImportedSoftwareTitle table updates or creates software titles (application records) for SaaS applications other than Microsoft Office 365.

Table 8. Application data mapping (ImportedSoftwareTitle table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
Not visible the application id	ExternalSoftwareTitleID	Not visible.
APPLICATION, and Display Name in application properties	FullName (up to 512 characters)	Application properties > General tab > Name
As above, APPLICATION, and Display Name in application properties	ProductName (up to 200 characters)	Application properties > General tab > Product
Managed Applications list > VENDOR	PublisherName (up to 200 characters)	Application properties > General tab > Publisher

Table 9. Application to License links (ImportedSoftwareTitleLicense table)

FSM object/label	FNMS staging fields	Example FNMS UI / Notes
	ExternalSoftwareTitleID	Not visible. Foreign key to the ImportedSoftwareTitle table, identifies an imported application
	ExternalSoftwareLicenseID	Not visible. Foreign key to the ImportedSoftwareLicense table, identifies a license created to match the imported data