| Author |
Variables seting data values in an expression
|
|
|
| All
We are having problems with assigning data to a Variable from an in coming message, when we run the Orchestration in debug we get a 'NULL Reference Exception Error'
We even tried fixed data values in our expression but again get the same error.
please note we are using 2004
cheers
Aly !
p.s this must be simple as we only want to set a value :-(
| |
| Matt Milner 2004-04-27, 11:37 am |
| have you initialized the variable to a new instance in the expression shape?
What does your expression look like and what type of variables are you
using?
Matt
"AlyD" <Alistair.Dickinson@islington.gov.uk> wrote in message
news:2123FC8A-6034-4FDF-9795-9DCC95E02738@microsoft.com...
> All
>
> We are having problems with assigning data to a Variable from an in coming
message, when we run the Orchestration in debug we get a 'NULL Reference
Exception Error'
>
> We even tried fixed data values in our expression but again get the same
error.
>
> please note we are using 2004
>
> cheers
>
> Aly !
>
> p.s this must be simple as we only want to set a value :-(
>
| |
|
| Hi matt
We are using strings that are defined within Biztalk (2004) they are defined in the orchestration view.
The expression looked somthing like the string below.
//some comments here
myString = myMessage.header.fieldId;
When running in debug the orchestration would stop at the expression with the NULL Error. Have you seen anything like this before, oh and we do appriciate the help.
Aly !
| |
| Matt Milner 2004-04-27, 4:35 pm |
| in the orchestration debugger, when you are in a breakpoint, can you see
that the promoted property you are trying to access has a value and is not
null?
Matt
"AlyD" <anonymous@discussions.microsoft.com> wrote in message
news:EE4B3B73-36E0-4D1E-BE45-02BDC388880A@microsoft.com...
> Hi matt
>
> We are using strings that are defined within Biztalk (2004) they are
defined in the orchestration view.
>
> The expression looked somthing like the string below.
>
> //some comments here
> myString = myMessage.header.fieldId;
>
> When running in debug the orchestration would stop at the expression with
the NULL Error. Have you seen anything like this before, oh and we do
appriciate the help.
>
> Aly !
>
| |
|
| Hi Matt
This is the problem the value for the promoted property is Null and causes the null error as mentioned before. While writing these notes we have deployed the orchestration again and this time we see a value so in theory it worked.
The problem is why did it work and what caused it to fail in the first place, was it down to us or a bug in the application.
Anyway after a reboot of the server and redeployment we got a result, so thanks for your help on this one.
Aly !
----- Matt Milner wrote: -----
in the orchestration debugger, when you are in a breakpoint, can you see
that the promoted property you are trying to access has a value and is not
null?
Matt
"AlyD" <anonymous@discussions.microsoft.com> wrote in message
news:EE4B3B73-36E0-4D1E-BE45-02BDC388880A@microsoft.com...
> Hi matt
defined in the orchestration view.[vbcol=seagreen]
> myString = myMessage.header.fieldId;
the NULL Error. Have you seen anything like this before, oh and we do
appriciate the help.[vbcol=seagreen]
>
|
|
|
|