Agentry - OData XPath Issue - Result found, of type 1, not string or nodeset

[Former Member]

I am seeing the following message repeated in my log file for each OData object that is returned in XML.

Incoming: context node is entry (Element)

+ Base XPath=default:feed/default:entry

  + Context Node=entry

    + XPath=/default:content/m:properties/d:WorkOrdersID/text()

      Result found, of type 1, not string or nodeset

      *** XML node for the unique ID not found: Can't determine object to store current object info in - Skipping row 360

Can anyone help me resolve the error in bold above?  I've tested my XPath in various testers online and it works fine.  I'm not sure what Agentry is looking for.

[ray_isada · Accepted solution]

Hi Christopher -

Did you resolve this issue? If not, here's some links that might help:

http://service.sap.com/sap/support/notes/1921547

Thanks,

Ray

[Former Member · Accepted solution]

I ended up fixing it by taking out a slash at the beginning of my XPath for each response mapping.

[bill_froelich · Accepted solution]

Christopher,

Glad you found a solution.  Please mark this Discussion with a Correct Answer and Helpful Answer where appropriate.  See http://scn.sap.com/community/support/blog/2013/04/03/how-to-close-a-discussion-and-why   Even if you discovered the solution without any outside contributions, it helps others to understand what the solution turned out to be.

--Bill