Windchill REST Services > Windchill REST Services Domain Capabilities > PTC Domains > PTC BOM Transformation Domain > Actions Available in the BOM Transformation Domain for Creating or Updating Downstream BOMs > ResolveDiscrepancies
  
ResolveDiscrepancies
The ResolveDiscrepancies action resolves discrepancies of the Auto status from the detected discrepancies. The action resolves the Auto discrepancies using the set of attributes that the DetectDiscrepancies action returns in its response.
See the Detecting and Resolving Discrepancies in the BOM Transformer topic in the Windchill Help Center, for more information.
The attributes in the request payload of the ResolveDiscrepancies action are described in the following table:
Request Attribute
Description
Required
CheckInDownstreamObject
Flag to specify whether the affected object in the downstream structure should be checked in after propagation or not upon resolving discrepancies.
Optional
DiscrepancyItems
Array to specify a set of attributes for a discrepancy that you want to resolve.
The set of attributes returned for each detected discrepancy in the DetectDiscrepancies response is specified as an input in the ResolveDiscrepancies request payload.
* 
• The request resolves discrepancies of the Auto status only. If you specify a set of attributes for a discrepancy of status other than Auto, the request ignores those discrepancies.
• DownstreamParentPath is required as an input attribute to propagate a newly added upstream part either to a different parent in the downstream or to the downstream root part. This input attribute is valid only for resolving discrepancies that have the criteria as Added Parts, status as Auto, and a single downstream parent part.
Use a solidus (/) to specify the path for the downstream root part.
• If the value of DownstreamParentPath is returned as empty ("") in the DetectDiscrepancies response, then the downstream equivalent parent part is considered for resolving the discrepancy.
Yes
DiscrepancyContext
Entity type from the DetectDiscrepancies request payload which specifies the source root part (here, upstream root part), target root part (here, downstream root part), upstream navigation criteria, and downstream navigation criteria attributes.
* 
DiscrepancyContext reviews the detected discrepancies internally, before those are resolved.
Yes