| Author |
Rules firing in test not in real - finding max date
|
|
|
| Hi
I have the following Biztalk message (simplified)
<votes>
<dates>
<mydate>1940-01-01</mydate>
<mydate>1943-01-01</mydate>
<mydate>1937-01-01</mydate>
<mydate>1987-01-01</mydate>
</dates>
<mostRecentDate>1900-01-01</mostRecentDate>
</votes>
I have made a rule:
if xml:FQN./votes.mostRecentDate < xml:FQN./votes/dates.mydate THEN
xml:FQN./votes.mostRecentDate = xml:FQN./votes/dates.mydate
I can see the rules firing when testing the policy but when running it
from the orchestration checking HAT tracing the rule does not fire?
I have used fullqualified names for the documenttype
Any input?
TIA
Ken
| |
| Tom Lysholt Hansen 2005-06-29, 5:51 pm |
| Are you passing a message instance to the "Call rule" shape in your
orchestration?
--
Regards
Tom Lysholt Hansen
GlobeTeam A/S
"Ken" wrote:
> Hi
>
> I have the following Biztalk message (simplified)
>
>
> <votes>
> <dates>
> <mydate>1940-01-01</mydate>
> <mydate>1943-01-01</mydate>
> <mydate>1937-01-01</mydate>
> <mydate>1987-01-01</mydate>
> </dates>
> <mostRecentDate>1900-01-01</mostRecentDate>
> </votes>
>
>
> I have made a rule:
>
> if xml:FQN./votes.mostRecentDate < xml:FQN./votes/dates.mydate THEN
> xml:FQN./votes.mostRecentDate = xml:FQN./votes/dates.mydate
>
> I can see the rules firing when testing the policy but when running it
> from the orchestration checking HAT tracing the rule does not fire?
>
> I have used fullqualified names for the documenttype
>
> Any input?
>
> TIA
> Ken
>
>
| |
|
| Hi Tom,
Yes i am passing a message instance to the Call rule shape. This is not
the only rule I have in this policy and the other rules in the policy
are working.
The other rules have hight priority than this one since they are
populating the dates I need to find max of.
Regards
Ken
| |
|
| Hi Tom
I solved it by moving the maxDateRule to another policy
must have been something about the fact not being updated in memory?
Ken
| |
| Tom Lysholt Hansen 2005-06-30, 6:00 pm |
| Great to hear that you solved the problem. It seems like a mystery to me
though that it didn't work before.
Your guess of the reason is at least as good as any I can come up with. :-)
I suppose we should be glad it isn't alway obvious - now we know that we'll
have jobs for a long time ;-)
--
Regards
Tom Lysholt Hansen
"Ken" wrote:
> Hi Tom
>
> I solved it by moving the maxDateRule to another policy
> must have been something about the fact not being updated in memory?
>
> Ken
>
>
|
|
|
|