Export and Import Issues Resolved
The following issues related to the Data Export and Import functionality were resolved in the 2023 R1 release.
• | Feature Version Now Marked As Mandatory in Import Template |
• | Data Import Template Now Successfully Updates Product Status |
• | Exported Feature Bundles Now Include New Features |
• | Product Import With Dependencies No Longer Fails When Using Config Option "Enable Product Lines for Products, Users, and Accounts" |
Feature Version Now Marked As Mandatory in Import Template
The Product Packaging Template (available under Administer > Import Data Objects > Data Import Templates) now indicates that specifying a feature version is mandatory. This is to avoid that producers attempt to create a product without a feature version, which would fail.
Data Import Template Now Successfully Updates Product Status
Previously, attempting to change the state of an existing product from “Draft” to “Deployed” using the Data Import template—either by setting the value of the DeployState column to Deployed or leaving it blank—resulted in an error. This issue no longer occurs.
Exported Feature Bundles Now Include New Features
Previously, when new features were added to an existing feature bundle, and this feature bundle was then exported into a .jar file and imported into another instance of FlexNet Operations, the new features were not imported. This issue has now been resolved and features are imported as expected.
Product Import With Dependencies No Longer Fails When Using Config Option "Enable Product Lines for Products, Users, and Accounts"
Previously, an issue occurred when importing a product linked to a product line while the configuration option Enable Product Lines for Products, Users, and Accounts was enabled. Attempting to import such a product with its dependencies would fail with the error "Cannot set product line. It is not part of the users account".
This issue has now been resolved by fixing the linking between the user account and the product line. Products are imported successfully and are correctly displayed in the Producer Portal.