Updating Windchill MPMLink Equivalent Link Preferences
Typically the appropriate context reference in an equivalent link and the view from the appropriate filter must match in order for an equivalent link to appear. The equivalent link contains a downstream context reference and an upstream context reference. These two references must be in accordance. The view reference specified in the currently applied filter is used and compared to the proper context reference in the equivalent link to determine if the link applies to this situation, and can thus be displayed. For example:
• In the Downstream Equivalent table in the upstream tree, the downstream context reference of the equivalent link must match the view of the current downstream filter, in order for the equivalent link to appear in the table. The downstream part iteration is verified with the downstream filter and then if it is still valid, the object can be displayed.
• In the Upstream Equivalent table in the downstream tree, the upstream context reference of the equivalent link must match the view of the current upstream filter, in order for the equivalent link to appear in the table. The upstream part iteration is verified with the upstream filter and then if it is still valid, the object can be displayed.
However, this behavior can be modified by using the Preference Management Utility to change the following preference: > . The following options are available:
• No: The default setting. Only the iterations of the equivalent objects that match the specified filter criteria are displayed.
• Yes: All iterations of the object are displayed, regardless of the specified filter.
• Only the latest revision of each branch: The most recently iterated versions of the object on each branch, that matches the specified filter criteria, are displayed.
In previous releases of Windchill MPMLink the options available for this preference were Yes and No. If you are updating from a release of Windchill MPMLink that contains these older options then any instances of equivalent links that were created with these options may appear incorrectly in a database. To fix this issue run the following SQL commands:
• update PreferenceInstance set value ='0' where ida3a4 in (select ida2a2 from PreferenceDefinition where name='Associativity.DisplayAllLinkedIterations') and value='true'
• update PreferenceInstance set value ='2' where ida3a4 in (select ida2a2 from PreferenceDefinition where name='Associativity.DisplayAllLinkedIterations') and value='false'