Inventory Object: ConsolidatedFileEvidence
ConsolidatedFileEvidence
objects are uploaded
to the ConsolidatedFileEvidence
table in the
operations (inventory) database. Multiple imports will merge
updated data with existing records, and add new records as
applicable.
ConsolidatedFileEvidence provides a simpler interface to specify files and their usage on computers. It combines the computer, file evidence and usage details into a single row.
Attributes are listed here in alphabetical order.
Property | Attributes | Notes |
---|---|---|
AccessMode
|
Alpha-numeric text (maximum 128 characters). Default: 1. Mandatory. Database key. |
The access mode of the file evidence. Leave this blank unless this row is a virtualized application. In that case choose one of the values below that matches your application or desktop virtualization infrastructure. Note: Strictly, this attribute may be null, because it forms
part of a compound database key. However, null values may cause import
errors (where this object does not get imported), and multiple records
from the same connection having nulls may cause data loss through
over-writing. It is therefore best practice to treat this field as
mandatory.
|
Company
|
Alpha-numeric text (maximum 100 characters). Default: . Mandatory. Database key. |
The company in the file header. Note: Strictly, this attribute may be null, because it forms
part of a compound database key. However, null values may cause import
errors (where this object does not get imported), and multiple records
from the same connection having nulls may cause data loss through
over-writing. It is therefore best practice to treat this field as
mandatory.
|
ComputerID
|
Unsigned integer (bigint ). Mandatory. Database key. |
The identifier used in the source connection for the computer. It must match the ComputerID from the Computer spreadsheet or the row will be ignored. |
Description
|
Alpha-numeric text (maximum 200 characters). Default: . Mandatory. Database key. |
The description in the file header. Note: Strictly, this attribute may be null, because it forms
part of a compound database key. However, null values may cause import
errors (where this object does not get imported), and multiple records
from the same connection having nulls may cause data loss through
over-writing. It is therefore best practice to treat this field as
mandatory.
|
FileName
|
Alpha-numeric text (maximum 256 characters). Mandatory. Database key. |
The name of the file used as evidence of software installation. For unix operating systems include the full path in the file name, including the opening '/'. For Windows operating systems the file path is specified in the FilePath column and this column must only contain the file name. |
FilePath
|
Alpha-numeric text (maximum 400 characters). May be null. |
The path of the file used as evidence of software installation. |
FileSize
|
Unsigned integer (int ). Default: 0. Mandatory. Database key. |
The size of the file in bytes. Note: Strictly, this attribute may be null, because it forms
part of a compound database key. However, null values may cause import
errors (where this object does not get imported), and multiple records
from the same connection having nulls may cause data loss through
over-writing. It is therefore best practice to treat this field as
mandatory.
|
FileVersion
|
Alpha-numeric text (maximum 100 characters). Default: . Mandatory. Database key. |
The version number of the file used as evidence of software installation. Note: Strictly, this attribute may be null, because it forms
part of a compound database key. However, null values may cause import
errors (where this object does not get imported), and multiple records
from the same connection having nulls may cause data loss through
over-writing. It is therefore best practice to treat this field as
mandatory.
|
Language
|
Alpha-numeric text (maximum 200 characters). May be null. |
The language in the file header. |
LastUsedDate
|
An ASCII string of alphanumeric characters and punctuation (length 10 characters). May be null. |
The last used date of the usage. |
NumberOfSessions
|
Unsigned integer (bigint ). May be null. |
The number of sessions that the file evidence was in use by the user specified in the UserID column during the usage tracking period. If multiple users used the same application on the computer, create one row for each user with usage. |
ProductName
|
Alpha-numeric text (maximum 200 characters). May be null. |
The product name in the file header. |
ProductVersion
|
Alpha-numeric text (maximum 200 characters). May be null. |
The product version number in the file header. |
StartDate
|
An ASCII string of alphanumeric characters and punctuation (length 10 characters). May be null. |
The start date of the usage. |
UserID
|
Unsigned integer (bigint ). Mandatory. Database key. |
The DOMAIN/SAMAccountName for the user that the file evidence was used by. If this software was used by multiple users, create one row for each user of the software on the computer. Note: Strictly, this attribute may be null, because it forms
part of a compound database key. However, null values may cause import
errors (where this object does not get imported), and multiple records
from the same connection having nulls may cause data loss through
over-writing. It is therefore best practice to treat this field as
mandatory.
|
FlexNet Manager Suite (On-Premises)
2023 R1