In Teamcenter it is possible to create an interdependent LOV such that the LOV description is displayed alongside the LOV value:
Where such functionality would be useful is when you have a short LOV value but need to use a longer LOV description to help the end user decide if the LOV value is the correct value to be selected i.e. CAGE Codes being a perfect example of this.
So the question is how to configure Solid Edge Embedded Client (SEEC) to use the Teamcenter LOV description that is associated to the LOV value along with the actual LOV value?
The instructions below assume that you have a basic working knowledge of both configuring SEEC and using BMIDE. Certain rudimentary steps that a person with the prerequisites should know how to complete have been omitted for instruction brevity.
1. Launch BMIDE.
2. Right-click on LOV and select “New LOV”:
3. Name the LOV and create the values and descriptions for each value in the LOV:
4. Double-click on the LOV to display the LOV tab:
5. Scroll down to the LOV Attachment section and attach the LOV to a TC property:
6. Select the LOV Attachment and “Edit” it:
7. In the Interdependent LOV Attachment form select the attached property and select “Attach Description”:
8. Select a property to attach the LOV description to:
9. The LOV Value is connected to one Teamcenter property. The LOV Description is connected to a different Teamcenter property. The LOV Description is now connected as an interdependent attachment to the LOV Value:
10. Deploy the BMIDE Template:
11. Validate the Interdependent LOV Attachment works in the RAC:
12. In SEEC create and deploy an attribute mapping to map the LOV Value to one SE property and the LOV Description to another SE property:
13. Launch SEEC and create a new Item. Notice in the CPD how there are square brackets the two Solid Edge properties and the second property value is grayed out. This indicates that these two properties are interdependent. When you select the LOV Value, the LOV Description is automatically populated into the second property based on the LOV Value picked: