Question3Replies465ViewsX RajaSekharC Member since 2015 15 posts SedgwickCMS Posted: 4 years agoLast activity: 4 years 6 months ago Closed Solved Service SOAP - RULE PARSE XML stream request doesn't set all the properties that is coming from external systemParse-XML does not map XML request data to ClipboardPage1. We have a soap-service rule which is being called by external app2. We are setting the properties in RULE PARSE XML stream request rule3. External App is sending all the parameters as part of their request4. But we see some properties are not being set on the page5. Screen shots attached.Performed the below steps:Perform 'revalidate and save' of these properties and it saves successfully.Performed 'revalidate and save' of the Parse-XML rule and it works this timeExecute Service-SOAP and still could not find the propertySince it couldn't find the property we see this error in tracer "Goal seek requires missing input property JurisChangeClaimStatus.dsClaimStatusRequest.ClaimStatusRequest.ClaimSubStatus"Please share if any one faced similar issues faced. Version Pega 7.1.8Incoming Request:--------------------------<?xml version="1.0" encoding="UTF-8"?><ns0:ChangeClaimStatus xmlns:ns0="urn:PegaRULES:SOAP:JurisChangeClaimStatus:JURIS"> <dsClaimStatusRequest> <ClaimStatusRequest><ClaimUID>4872822.904</ClaimUID><ClientId>1970</ClientId><FileNum>151217000000002</FileNum><ProcUnit>670</ProcUnit><VendorId>PEG</VendorId><UserID>SYSTEM</UserID><ClaimStatus>O</ClaimStatus><ClaimSubstatus>A</ClaimSubstatus><ClaimTier>FeatherTouch</ClaimTier> <DenialType> </DenialType><Appealed>no</Appealed> <Overturned>no</Overturned><Reopened>no</Reopened><ReasonCode></ReasonCode> </ClaimStatusRequest> </dsClaimStatusRequest> </ns0:ChangeClaimStatus> Data Integration ReplyI also have this Question (0) FacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 4 years agoARVINDMALAV PEGA replied to RajaSekharCHi Raja,Can you please use DSS Pega-IntegrationEngine / SwitchToOldAssembler= true , restart server and then check if mapping is correct? Posted: 4 years agoRajaSekharC SedgwickCMS replied to ARVINDMALAVTried this option, but couldn't resolve the issue. We found the issue is the case sensitivity from incoming request vs pega parse xml which resolved the issue. Posted: 4 years agoGangababu PEGA replied to RajaSekharCPlease share the stacktrace when issue occurred.