|
Home > Archive > BizTalk Server General > November 2005 > Distinguished field error in BRE
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Distinguished field error in BRE
|
|
|
| I have a status field (child element) from a schema as a distinguished field.
In an Orchestration I perfrom a call rules. In the policies rule if a field
is > 1000 I set the status field to true. In the orchestration I have a
decide shape where in the expression I check that the status field is set to
True. Unfortuantely I get an error (see below). It seems to be because it
cant find the status field in the schema.
I have followed the usual rules of making sure the document and message type
are the same and when I use a non distingusihed field it works (in that I
used another field) but I need the field to be distinguished to check the
results in an expression.
What is the error?
Uncaught exception terminated service
BizTalk_Server_Project3.Orchestration_1(c7c553b1-bf6c-9029-64c8-0f2aed1bb23e), instance 5e41043b-bf6b-469c-bafc-6f5fe791b7eb
An exception occurred inside the rule engine instance executing policy "PO2".
Exception type: PolicyExecutionException
Source: Microsoft.RuleEngine
Target Site: Void ExecuteInternal(System.Object)
Help Link:
Additional error information:
Field "*[local-name()='Status' and namespace-uri()='']" does not exist in
XML document "BizTalk_Server_Project3.PsoftOrder", selector "/Psofthead".
Exception type: RuleEngineRuntimeFieldNotDefinedExceptio
n
Source: Microsoft.RuleEngine
Target Site: Void ProcessException(System.Exception)
Help Link:
Additional error information:
For more information, see Help and Support Center at
| |
| Keith Newton 2005-11-17, 6:10 pm |
| Hi,
Does the message going into the call rules shape already have a status
element either defaulted to true or false ? To keep things simple you will
need to supply the element with a default value upfront and then use the
logic in your rules to change it based on whatever conditions you want.
Cheers, Keith
"Nickg" <Nickg@discussions.microsoft.com> wrote in message
news:8D40D2B5-73A5-4A85-844F-E9F5C0FA38FF@microsoft.com...
>I have a status field (child element) from a schema as a distinguished
>field.
> In an Orchestration I perfrom a call rules. In the policies rule if a
> field
> is > 1000 I set the status field to true. In the orchestration I have a
> decide shape where in the expression I check that the status field is set
> to
> True. Unfortuantely I get an error (see below). It seems to be because it
> cant find the status field in the schema.
>
> I have followed the usual rules of making sure the document and message
> type
> are the same and when I use a non distingusihed field it works (in that I
> used another field) but I need the field to be distinguished to check the
> results in an expression.
>
> What is the error?
>
> Uncaught exception terminated service
> BizTalk_Server_Project3.Orchestration_1(c7c553b1-bf6c-9029-64c8-0f2aed1bb23e),
> instance 5e41043b-bf6b-469c-bafc-6f5fe791b7eb
>
> An exception occurred inside the rule engine instance executing policy
> "PO2".
>
> Exception type: PolicyExecutionException
> Source: Microsoft.RuleEngine
> Target Site: Void ExecuteInternal(System.Object)
> Help Link:
> Additional error information:
>
> Field "*[local-name()='Status' and namespace-uri()='']" does not exist in
> XML document "BizTalk_Server_Project3.PsoftOrder", selector "/Psofthead".
>
> Exception type: RuleEngineRuntimeFieldNotDefinedExceptio
n
> Source: Microsoft.RuleEngine
> Target Site: Void ProcessException(System.Exception)
> Help Link:
> Additional error information:
>
>
>
> For more information, see Help and Support Center at
| |
|
| Keith,
thanks, that worked a treat.
Nick.
"Keith Newton" wrote:
> Hi,
>
> Does the message going into the call rules shape already have a status
> element either defaulted to true or false ? To keep things simple you will
> need to supply the element with a default value upfront and then use the
> logic in your rules to change it based on whatever conditions you want.
>
> Cheers, Keith
>
> "Nickg" <Nickg@discussions.microsoft.com> wrote in message
> news:8D40D2B5-73A5-4A85-844F-E9F5C0FA38FF@microsoft.com...
>
>
>
|
|
|
|
|