Hi
I ran into this issue today. It turned out that the error occured in an expression shape that used xpath to get a value from a message into a variable.
Having been using xpath expressions inside my orchestrations for a long time, I am really not used to having them fail on me And this particular xpath expression was copied from the "Instance XPath" property of the element in the schema editor. So it shouldn't fail. I did add a "[1]" to the xpath because I needed to access the first element of a re-occuring element, but still - not something I hadn't done plenty of times before.
Actually, it took quite some time before I discovered what was wrong. My expression was:
DeliveryDate = xpath(OrderMessage, "/*[local-name..........");
and I needed to change it to
DeliveryDate = xpath(OrderMessage, "string(/*[local-name..........)");
Again, something I have done a million times... this time I just forgot it. And honestly, I really don't think the error message gives a very good idea of what is wrong...
Hope this gets indexed and someone later on will find it helpful
-- eliasen
Remember Me
a@href@title, b, blockquote@cite, em, i, strike, strong, sub, sup, u
Theme design by Jelle Druyts
Powered by: newtelligence dasBlog 2.3.9074.18820
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.
© Copyright 2024, Jan Eliasen
E-mail