Regenerating Type-Level Database Views
This section only applies to customers who have used the Create Database View action to create a database view definition for a type and its attributes. Type-level database view definitions generated using this action must be recreated following the upgrade to PTC FlexPLM 11.0 M030.
This action was previously available by following these steps:
1. Select > .
2. Select a root type.
3. From the list above the classification tree, select Create Database View.
4. From the classification tree, select a subtype.
5. Click Generate Database View.
For upgrading customers, the process results in the following situations:
• All database views are automatically dropped by the upgrade process.
• Out-of-the-box required database views are recreated by the upgrade process.
• Type-level database view definitions previously generated by the customer are not automatically recreated during the upgrade process.
If customers have generated one or more database view definitions, and they have used the view definition as it was originally generated with no customization to the VIEW definition DDL, they must regenerate all type-level database views using the DBViewGeneratorHelper command-line utility. For more information, see "Creating Database Views" in the Windchill Help Center.
If customers have customized the view definition created by the utility in an earlier release of PTC FlexPLM, they must apply equivalent customizations to the newly generated type-level view definition. This action must be done in addition to regenerating the database view definition using the DBViewGeneratorHelper command-line utility.
Customers cannot rely on previously captured type-level database view definitions if the view was created using the Create Database View action. Customers must instead regenerate the type-level database view definition. Numerous changes in the database schema and attribute definitions resulting from convergence on the WindchillType and Attribute Management utility require new view definitions to be generated.
While the columns holding global attribute values are mapped to a meaningful name, customers should be aware of the following changes in the newly generated VIEW definition SQL:
• The underlying database column names for global attributes will change.
• Each alias for a database column included in the view might change.
• The datatype of a column included in the query might change.
• The number of columns used to store a value of an attribute might change.
Customers are responsible for refactoring any customizations that rely on the type-level database views generated using the DBViewGeneratorHelper command-line utility. Every customization that uses a type-level database view definition must be validated by the customer to ensure the customization works as expected. This validation must occur regardless of whether the view definition was customized after it was regenerated.