Updating Equivalent Links in the Downstream Structure
You can update a single or multiple out-of-date equivalent links between the downstream parts and their currently linked upstream iteration. You can also update the equivalent links in the context of change (change task or change notice).
You can update the out-of-date equivalent links by specifying the downstream equivalent parts and upstream and downstream navigation criteria in the request body. If you do not specify the navigation criteria, the System Default filter is applied.
You can also update the out-of-date equivalent links along with propagating information from upstream to downstream.
The DoCopyOver flag is an optional attribute to specify whether you want to propagate the information from upstream to downstream or not.
When an out-of-date equivalent link is updated, a new equivalent link is created to the latest valid upstream iteration.
Example: Updating Multiple Equivalent Links in the Downstream Structure
This example shows you how to update two out-of-date equivalent links by specifying two downstream equivalent parts, an inline downstream navigation criteria, and upstream navigation criteria ID in the request body. In this example, the DoCopyOver flag is specified as true and the Ask To Carry Over During Create or Update preference in Windchill is set to Yes. This example shows you how to update two out-of-date equivalent links along with propagating information from upstream to downstream. Use the following POST URI with the request body:
URI
POST Windchill/servlet/odata/BomTransformation/UpdateToCurrentUpstreamEquivalents
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"DownstreamParts": [
{
"ID": "OR:wt.part.WTPart:503586"
},
{
"ID": "OR:wt.part.WTPart:503587"
}
],
"DoCopyOver": true,
"UpstreamNavigationCriteria": {
"ID": "OR:wt.filter.NavigationCriteria:503393"
},
"DownstreamNavigationCriteria": {
"ApplicableType": "PTC.ProdMgmt.Part",
"ApplicationName": null,
"ApplyToTopLevelObject": false,
"Centricity": false,
"ConfigSpecs": [
{
"@odata.type": "#PTC.NavCriteria.WTPartStandardConfigSpec",
"WorkingIncluded": true,
"View": "Manufacturing",
"LifeCycleState": null,
"Variation1": null,
"Variation2": null
}
],
"Filters": [],
"HideUnresolvedDependents": false,
"UseDefaultForUnresolved": false
}
}
The request updates the equivalent links and returns the up-to-date status and other information for each of the two new equivalent links that are created.
Example: Updating Multiple Equivalent Links in the Downstream Structure in the Context of Change
This example shows you how to update two out-of-date equivalent links in the context of change by specifying two downstream equivalent parts, downstream navigation criteria ID, upstream navigation criteria ID, and a change task OID in the request body. In this example, the DoCopyOver flag is specified as true and the Ask To Carry Over During Create or Update preference in Windchill is set to Yes. Use the following POST URI with the request body:
URI
POST Windchill/servlet/odata/BomTransformation/UpdateToCurrentUpstreamEquivalents
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"DownstreamParts": [
{
"ID": "OR:wt.part.WTPart:198452"
},
{
"ID": "OR:wt.part.WTPart:198462"
}
],
"DoCopyOver": true,
"UpstreamNavigationCriteria": {
"ID": "OR:wt.filter.NavigationCriteria:196343"
},
"DownstreamNavigationCriteria": {
"ID": "OR:wt.filter.NavigationCriteria:196348"
},
"ChangeOid": "VR:wt.change2.WTChangeActivity2:197680"
}
The request updates the equivalent links and returns the up-to-date status and other information for each of the two new equivalent links that are created. The request adds the iterated downstream parts in the Resulting Objects table of the change object specified in ChangeOid.