I have encountered another problem with parsing process. Although the problem occurs in the xpath node, I think it might have a connection to the parsing node itself.
I attach an example workflow. If you can take alook at it, it would be great.
looks like the secons XPath node uses the wrong input column; it's set to "Document" (and thus always returns the first price element), but it should be "tarih" I suppose.