Still having problems…
Whether I use a pipeline or not, I cannot get my orchestrations to work.
Here’s the deal:
If I simply have an orch that receives and sends the message back out, and does nothing with the data, it works. The second I put in any type of logic in there to do something with the data, I get an error in HAT stating \”Error in accessing the part data or one of its fragments. The part or fragment may not exist in the database.\” So all of a sudden, BTS forgets that my schema was valid?
In my orchestration, I call a .NET component that transforms the original name/value paired message to tags…this component returns the message to me as an XmlDocument which I have built a schema for to support the returned message. I am then supposed to run several processes with the transformed message in a happy world.
I don’t believe the error is pertaining to the new transformed message however, as the Service Class reporting the error in HAT is ‘Messaging’ rather than ‘Orchestration’.
Now, when this ‘works’, I will be receiving multiple messages sharing the same namespace/root node….I thought this would be easy with BTS 2004, turns out, I’m better off running manual code solutions so far.
Can anybody bring hope?
-Rich