This article describes the Data Platform v5 extractor fields that are supported in Flexera One.
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:
Notes:
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 |
|||||
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 |
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 |
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 |
Feb 03, 2022 04:00 PM - edited Nov 27, 2023 08:08 PM
Are we able to have this published in to https://docs.flexera.com/ for Data Platform / IT Visibility?
@kstaude Thanks for your suggestion. We'll look into that👍