cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
 

Data Platform v5 standalone extractors can be used in Flexera One. However, there are limitations on the contents of the extractor files. To make a Data Platform extractor functional in Flexera One, you might need to make changes to some fields in the extractor files.

The following tables describe:

  • Mappings between the source fields in the Data Platform v5 extractor files and their equivalent target fields in Flexera One Technology Resource Services (TRS)
  • Special behaviors and limitations of each field.

Notes:

  1. Each mapping table is named for the imported TRS record.
  2. In each mapping table, one or more Key Fields are identified. Key Fields are the fields that are used in the involved data table files to relate records together and must exist in each file; otherwise, the process will fail.
  3. The ResourceID field is a Key Field for all sources, as it is the common key to connect records and to uniquely identify the device from multiple imports.
  4. If a file is marked as Required, it must exist in the extractor, otherwise the process will fail.
  5. If a file is marked as Grouped, the data in the file is first grouped by the Key Fields prior to being joined with other files. When a file is Grouped, duplicate Key Fields are anticipated. When a file is not Grouped, duplicate Key Fields must not exist, otherwise the process will fail.
  6. If a Grouped file is also marked as “First taken”, only the first record of the duplicate records in that file will be used, according to the record order in the file unless otherwise specified.

 

Table 1. Mappings for Computer records

Each “Computer” record in TRS represents the hardware details about a device.

Key Fields(s): ResourceID

Source file

Required

Grouped

Source Field

TRS Target Field

Special Behaviour / Limitation

GS_COMPUTER_SYSTEM

Name0

Name

Ignored if System.csv exists

Model0

ModelNo

 

Manufacturer0

Manufacturer

 

Domain0

Domain

DomainFlat

 

NumberOfProcessors0

NumberOfProcessors

 

UserName0

LastLoggedonUser

 

GS_LOGICAL_DISK

Size0

HddTotalSpace

Sum of grouped records

GS_NETWORK_ADAPTER_CONFIGUR

MACAddress0

[]NetworkInfo.Mac

 

IPAddress0

[]NetworkInfo.IPv4Address

[]NetworkInfo.IPv6Address

Attempts to detect pattern and places in appropriate field

GS_PROCESSOR

Name0

[]ProcessorInfo.Name

 

MaxClockSpeed0

[]ProcessorInfo.ClockSpeedMax

 

Manufacturer0

[]ProcessorInfo.Manufacturer

 

GS_X86_PC_MEMORY

TotalPhysicalMemory0

TotalMemory

 

GS_OPERATING_SYSTEM

✔ - First taken, ordered by Name0

Name0

OperatingSystem

 

Caption0

   

Version0

   

CSDVersion0

   

Manufacturer0

   

GS_SYSTEM_ENCLOSURE

✔ - First taken

SerialNumber

SerialNumber

Only used if GS_PC_BIOS did not supply it

ChassisType

ChassisType

 

GS_PC_BIOS

SerialNumber0

SerialNumber

 

GS_VIDEO_CONTROLLER

Name0

DisplayAdapterCount

Count of grouped records

GS_WORKSTATION_STATUS

LASTHWSCAN

InventoryDate

 

System

Name

Name

 

Domain

Domain

DomainFlat

 

Obsolete

 

If 1, the record will be ignored

Note: When the GS_COMPUTER_SYSTEM file and System file are both provided, the Name and Domain fields will be taken from the System file if the value is not empty.

 

Table 2. Mappings for InstallerEvidence records

Each "InstallerEvidence" record in TRS is an array of all the installed software on a device. It is expected that the ResourceIDs specified here can be linked back to those in the "Computer" stream; however, this is not enforced.

Key Fields(s): ResourceID, AddRemove_Key (conditional)

Source file

Required

Grouped

Source Field

TRS Target Field

Special Behaviour / Limitation

AddRemove

✖ - Falls to "AddRemove_AH" and "AddRemove_AU" if missing

✔ - Only most recent install date for any distinct record

DisplayName

Title

 

Version

Version

 

Publisher

Manufacturer

 

InstallDate

InstallDate

 

ProdID

ProductCode

 

AddRemove_AH

✔ - Only if "AddRemove" is not supplied

✔ - Only most recent install date for any distinct record

AddRemove_Key

 

Used as join criteria to AddRemove_AU

ProdID

ProductCode

 

InstallDate

InstallDate

 

AddRemove_AU

✔ - Only if "AddRemove" is not supplied

AddRemove_Key

 

Used as join criteria to AddRemove_AU

DisplayName

Title

 

Version

Version

 

Publisher

Manufacturer

 

 

Table 3. Mappings for OSEvidence records

Each "OSEvidence" record in TRS is an array of all the operating systems on a device. This is mainly designed to cover the situations where a single machine can be "dual booted", so the format can supply all the operating systems that a device has. It is expected that the ResourceIDs specified here can be linked back to those in the "Computer" stream; however, this is not enforced.

Key Fields: ResourceID

Source file

Required

Grouped

Source Field

TRS Target Field

Special Behaviour / Limitation

GS_OPERATING_SYSTEM

Name0

Name

 

Caption0

Caption

 

Version0

Version

 

CSDVersion0

CsdVersion

 

Manufacturer0

Manufacturer

 
Was this article helpful? Yes No
No ratings
Comments
kstaude
By
Level 4

Are we able to have this published in to https://docs.flexera.com/ for Data Platform / IT Visibility?

JingQian
By Level 3 Flexeran
Level 3 Flexeran

@kstaude  Thanks for your suggestion. We'll look into that👍

Version history
Last update:
‎Jul 09, 2024 09:12 PM
Updated by: