- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Suite Known Issues
- :
- Known Issue: Inventory import writers are executed every time inventory data is uploaded from a beac...
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Known Issue: Inventory import writers are executed every time inventory data is uploaded from a beacon (IOK-1004611)
Known Issue: Inventory import writers are executed every time inventory data is uploaded from a beacon (IOK-1004611)
Summary
When inventory data is uploaded from a beacon to a FlexNet Manager Suite (on premises) application server, a process to perform a full inventory import (including running the “writers” phase of the import) is initiated. This process is run in addition to the full inventory import process that (by default) runs each night.
Mitigation
It may be preferable to have a full import process only executed once per day, and not whenever inventory data is uploaded from a beacon. It is possible to configure FlexNet Manager Suite so that when inventory data is uploaded from a beacon the data will only be staged in the database for subsequent processing the next time the inventory import process runs.
This can be configured by running the following query against the compliance database:
UPDATE cts SET SettingValue = '0' FROM dbo.ComplianceTenantSetting cts JOIN dbo.SettingName sn ON sn.SettingNameID = cts.SettingNameID WHERE sn.Name = 'PackageUploadTriggersWriters'
Fix status
This issue is under consideration to be addressed in a future FlexNet Manager Suite release.
Other information
Affected components: Inventory import (read/write/export)
Master issue ID: IOK-1004611
Also known as: FNML-77313
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.
- Mark as Read
- Mark as New
- Permalink
- Report Inappropriate Content
FYI... I had to change the query as follows (because SettingName is not a valid column name in the SettingName table in 2021 R1):
SET SettingValue = '0'
FROM dbo.ComplianceTenantSetting cts
JOIN dbo.SettingName sn ON sn.SettingNameID = cts.SettingNameID WHERE sn.Name = 'PackageUploadTriggersWriters'
- Mark as Read
- Mark as New
- Permalink
- Report Inappropriate Content
Thanks for spotting the typo @DiannaB! We'll get that fixed in this article.