cancel
Showing results for 
Search instead for 
Did you mean: 

Migration of the working code -can 't parse the XML element

IntegrationCPI
Participant
0 Kudos

Hi , While migrating the working code to new version , XML is picked from the message and but unable to parse the value of the xml element .However when values are Hard coded it works fine . Since there was change in code wondering what is causing this error in the new system . Initially thought ,this could be either because of the size of the XML file which is 2.4 MB or wrong XSL path . However i can see the entire XML content  in the transaction log and also there is no change in the  code as the same code is already working in the older production version Any help would be greatly appreciated. Thanks, Kishore K V

Accepted Solutions (0)

Answers (2)

Answers (2)

IntegrationCPI
Participant
0 Kudos

Hi , I did Refresh of all the transaction and web folder . but still the same issue The main issue is XML.loadConfig.XmlContent{//*[plant='#Transaction.plant#']/XXX}  . The value of the plant is not getting parsed . Thanks, Kishore K B

swaroop_anasane
Active Contributor
0 Kudos

Hi Kishore,

Any specific error you see?

Regards,

Swaroop

IntegrationCPI
Participant
0 Kudos

Hi , The problem is while extracting the value from the XML . loadConfig.XmlContent{//*[plant='#Transaction.plant#']/XXX}  - It is unable to extract the value but same works in the production env . It is case with all the transactions migration is from MII 12 to MII 15. Thanks, Kishore K V