Device Data Extract

The first time the Device Data Extract job runs it creates a snapshot of device events (including FlexNet Embedded devices and license servers) from the day prior to the day the job runs. (Device and license servers created or updated from 00:00:00 to 23:59:59, FlexNet Operations server time, on the previous day are captured when the job runs). Subsequently, when this job runs, it creates a snapshot from the end time of the last successful run to the current time.

A successful run of this job creates a comma-separated value (CSV) file. The job output is a snapshot of devices and license servers created or updated; it does not include device history data.

The first line of the job output contains the header information for the table described by the CSV. If no devices were created or updated in the job period, the CSV output includes only the header row content.

Sample Output: Device Data Extract Job

DeviceID, Type, IDType, BackupDeviceID, Alias, DeviceSeries, PublisherName, DeviceAccountID, DeviceAccountName, Status, DeviceUserEmail, BaseProduct, SiteName, Notes, ActivationID, LicenseOwnerID, LicenseOwnerName, ProductName, ProductVersion, QtyOnDevice, LicenseStatus, LicenseModel1, LicenseModel2, LicenseModel3, IsPermanent, ExpirationDate

Device-1, CLIENT, STRING, , , FLX_CLIENT_SERIES, fnedemo, O1, O1, ACTIVE, , , , CLS-SITE, ba7f-6048-68a5-4630-b8b1-502a-8548-a115, O1, O1, 3rdLevelUpgradeProd, 3.0, 2, LICENSE_GENERATED, Embedded Counted, , , NO, Sat Nov 05 00:00:00 PDT 2016,

Device-2, CLIENT, STRING, , , FLX_CLIENT_SERIES, fnedemo, O1, O1, ACTIVE, , FNP_FNE, , , ba7f-6048-68a5-4630-b8b1-502a-8548-a115, O1, O1, 3rdLevelUpgradeProd, 3.0, 12, LICENSE_GENERATED, Embedded Counted, , , NO, Sat Nov 05 00:00:00 PDT 2016,

Device-2, ,,,,,,,,,,,,, 8793-2031-9c1e-4e4a-a5a8-4ff4-8d91-3d70, O1, O1, FNP_FNE, 3.0, 14, LICENSE_GENERATED, Embedded Uncounted, , , NO, Sat Dec 03 00:00:00 PST 2016,

Device-3, CLIENT, STRING, , , FLX_CLIENT_SERIES, fnedemo, O1, O1, ACTIVE, , , , , ba7f-6048-68a5-4630-b8b1-502a-8548-a115, O1, O1, 3rdLevelUpgradeProd, 3.0, 3, LICENSE_GENERATED, Embedded Counted, , , NO, Sat Nov 05 00:00:00 PDT 2016,

...

Notice that, for license servers or devices that have multiple activation IDs, FlexNet Operations structures the CSV output so that a new row appears for each additional activation ID on a given device. On these extra rows, the device ID of the device or license server is repeated, the device details between the device ID and the additional activation ID are left empty, and the additional activation ID (as well as information specific to that activation ID) follows. (See “Example for Multiple Activation IDs on a Device,” below.)

Example for Multiple Activation IDs on a Device

DeviceID, ..., ActivationID, ...

Device01, ..., Activation101, ...,

Device02, ..., Activation201, ...

Device02, ..., Activation202, ...

Device03, ..., Activation301, ...

...

Above, Device02 has two activation IDs mapped to it: Activation201 and Activation202. Device01 and Device03 both have only one activation ID mapped. In an actual output file, the row for Device02 and Activation201 would show the type, the type ID, the alias (if any), and so forth. Extra rows for Device02 would not show those values.

Also notice that, for license servers or devices with activation IDs that have more than one product, FlexNet Operations creates an extra row for each additional product. This follows a very similar pattern to the one used to generate extra rows for multiple activation IDs. In the multiple-products case, both the device ID and the activation ID are repeated, and then additional product name (as well as different information specific to that product) follows. In these extra rows, the device details between the device ID and the activation ID, and the license owner details between the activation ID and the product name, are left empty. (See “Example for Multiple Products in an Activation ID,” below.)

Example for Multiple Products in an Activation ID

DeviceID, ..., ActivationID, ..., ProductName, ...

Device01, ..., Activation101, ..., Product1A, ...

...

Device04, ..., Activation401, ..., Product4A, ...

Device04, ..., Activation401, ..., Product4B, ...

Device04, ..., Activation401, ..., Product4C, ...

Device05, ..., Activation501, ..., Product5A, ...

...

Above, Device04 has one activation ID mapped to it: Activation401. Activation401 has three products: Product4A, Product4B, and Product4C. Each additional product after Product4A causes an extra row to be generated for Device004.

Extra rows are generated for both activation IDs and products. In the case of multiple activation IDs, the device ID is repeated. In the case of multiple products, the device ID and the activation ID are repeated.