Smartsheets can include attributes linked from classifications for onboarding and maintenance of data in STEP.
Important: Currently, in order to get the classification linked attributes exported properly when using this parameter, the user must select the exact classification node that the attribute(s) are linked to. Additionally, not all LOV-based attributes are handled correctly during export, and do not always display as read-only in the Smartsheet.
The parameter 'Classification roots for inherited attributes' found on the 'Select Format' step of the Export Manager wizard, allows system administrators to configure one or more Product Classification Links Types when configuring a Smartsheet. When setting up a Smartsheet export, it is essential to ensure that the attributes linked to the classification are valid for exported object types. In case if the attributes with valid object types are not linked, the attributes will not export in the Smartsheet.
When the 'Classification roots for inherited attributes' parameter is configured, meaning classification root nodes have been selected and displayed in the field, the Export Manager determines the valid attributes for new products in the product category. If a Product Classification Link type allows for inheritance of attribute validity from the linked classification then also the Export Manager determines the valid attributes for new products in the product category. These attributes are included in the Smartsheet output.
If nothing has been configured for 'Classification roots for inherited attributes,' there are no changes to the current way of determining what should be exported.
If one or more Classification roots have been configured, the system checks for any attributes that are linked below the Classification roots. It checks whether Smartsheet usage is configured as a Template export (for onboarding new products) or as a Data export (for maintaining product data).
When the Smartsheet format is selected, Classification roots for inherited attributes parameter checks for:
- Each product category selected for export has a Product Classification Link type to one or more nodes below the classification root. If nothing is selected there are no changes to the current way of determining what should be exported.
- If the link type 'Inheritance of Specification Attributes / Data Container Types' is configured as 'No,' there are no changes to the current way of determining what should be exported.
- If the link type 'Inheritance of Specification Attributes / Data Container Types' is configured as 'Yes,' it finds all attributes below the root valid for the exported products via classification links. If these attributes are mapped in the export configuration, then the STEP XML generated also includes valid attributes from the product hierarchy.
- If the link type 'Ignore LOV Filter definitions on inherited Attributes for links' is configured as 'No,' there are no changes to determining how LOV values should be exported.
- If the link type 'Ignore LOV Filter definitions on inherited Attributes for links' is configured as 'Yes,' it determines which LOV attributes have a filter applied and collects valid values for the selected product category.
For onboarding new products, the attribute validity will apply via Classification inheritance for each product category, and the filtered LOV values will be the same for all new products created. The Smartsheet file will have attributes that are valid via classification links.
For maintaining product data, the Smartsheet includes attribute columns that are valid via classification links. If the attribute is not valid for a given product row, the intersecting cell will be read-only. When the LOV attributes have a filter applied, each product row only allows valid values.
Important: Attributes that are inherited through a product-classification link cannot be exported to a Smartsheet.
For more information on configuring these functions, refer to the Smartsheet Data and Template Configurations topic of the documentation here.
For more information on maintaining Classification roots, refer to the Classification Roots for Inherited Attributes Use Cases topic of the documentation here.