Not all of my distinguised properties are showing up in the expression
editor.  Is there a limitation on distinguished properties on different node
levels??

Here is an example:
<request>
<DBConnection>
<Database />
<User />
</DBConnection>
<CaseInformation>
<Product />
<Reason />
</CaseInformation>
</request>

I have promoted Database, User, Product, and Reason fields as distinguished
fields to be used in my orchestration.  When using the expression shape, I
can access the DBConnection fields, but not the CaseInformation fields.

MessageName.Database and MessageName.User are valid, but
MessageName.Product, and MessageName.Reason create an error.

Is there anything I am overlooking??  Any help will be greatly appreciated!!


Thanks

[ Post a follow-up to this message ]

Are you getting a runtime error or designtime one?
Do you see the erroneous properties with intellisense?
If its a runtime error, please verify the XPath associated with these fields
against the message body at the time of exception.

Regards
Dev

"Mike" <Mike@discussions.microsoft.com> wrote in message
news:8297CE24-69FF-4E75-B844-B1C57447C21C@microsoft.com...
> Not all of my distinguised properties are showing up in the expression
> editor.  Is there a limitation on distinguished properties on different
node
> levels??
>
> Here is an example:
> <request>
>   <DBConnection>
>     <Database />
>     <User />
>   </DBConnection>
>   <CaseInformation>
>     <Product />
>     <Reason />
>   </CaseInformation>
> </request>
>
> I have promoted Database, User, Product, and Reason fields as
distinguished
> fields to be used in my orchestration.  When using the expression shape, I
> can access the DBConnection fields, but not the CaseInformation fields.
>
> MessageName.Database and MessageName.User are valid, but
> MessageName.Product, and MessageName.Reason create an error.
>
> Is there anything I am overlooking??  Any help will be greatly
appreciated!!
>  
>
> Thanks

[ Post a follow-up to this message ]

This is a designtime.  When I try and build it, I get the error.  I have the
red squigly underneath the property that isn't valid.  In intellisence, I ca
n
see .DBConnection.Database, but not .CaseInformation.Product (Sorry, I
mistyped on my first post).  The XPATH is valid.

"Devdutt Patnaik" wrote:

> Are you getting a runtime error or designtime one?
> Do you see the erroneous properties with intellisense?
> If its a runtime error, please verify the XPath associated with these fiel
ds
> against the message body at the time of exception.
>
> Regards
> Dev
>
> "Mike" <Mike@discussions.microsoft.com> wrote in message
> news:8297CE24-69FF-4E75-B844-B1C57447C21C@microsoft.com... 
> node 
> distinguished 
> appreciated!! 
>
>
>

[ Post a follow-up to this message ]

Did you try promoting them into Property Fields and see whether that gives
the same problem as Distinguished Fields?
Did you try demoting and re-promoting them?
Regards
Dev

"Mike" <Mike@discussions.microsoft.com> wrote in message
news:BF3B0971-142A-4AC0-B9AB-DD134676DF4C@microsoft.com...
> This is a designtime.  When I try and build it, I get the error.  I have
the
> red squigly underneath the property that isn't valid.  In intellisence, I
can[vbcol=seagreen]
> see .DBConnection.Database, but not .CaseInformation.Product (Sorry, I
> mistyped on my first post).  The XPATH is valid.
>
> "Devdutt Patnaik" wrote:
> 
fields[vbcol=seagreen] 
different[vbcol=seagreen] 
shape, I[vbcol=seagreen] 
fields.[vbcol=seagreen] 

[ Post a follow-up to this message ]

Yes, I have redone the promotions many times.  Maybe I'm wrong, but I am
working on the assumption that you use Promoted Properties for content based
routing, and Distinguised Properties are used in the orchestration flow.

Mike

"Devdutt Patnaik" wrote:

> Did you try promoting them into Property Fields and see whether that gives
> the same problem as Distinguished Fields?
> Did you try demoting and re-promoting them?
> Regards
> Dev
>
> "Mike" <Mike@discussions.microsoft.com> wrote in message
> news:BF3B0971-142A-4AC0-B9AB-DD134676DF4C@microsoft.com... 
> the 
> can 
> fields 
> different 
> shape, I 
> fields. 
>
>
>

[ Post a follow-up to this message ]

Has "CaseInformation" a MaxOccurs of more than 1?

Danny.

"Mike" wrote:
[vbcol=seagreen]
> Yes, I have redone the promotions many times.  Maybe I'm wrong, but I am
> working on the assumption that you use Promoted Properties for content bas
ed
> routing, and Distinguised Properties are used in the orchestration flow.
>
> Mike
>
> "Devdutt Patnaik" wrote:
> 

[ Post a follow-up to this message ]

The CaseInformation Parent has no MinOccurs or MaxOccurs, but the child
elements, Product and Reason, have a MinOccurs of 0 and a MaxOccurs of 1.
Same with the DBConnection node.

"Danny Buysse" wrote:
[vbcol=seagreen]
> Has "CaseInformation" a MaxOccurs of more than 1?
>
> Danny.
>
> "Mike" wrote:
> 

[ Post a follow-up to this message ]

I think I fixed my problem.  For some reason it was not creating a property
tag at the top of my schema for the CaseInformation fields.  I went in
manually and added the tags with the correct XPATH and am now able to
compile.

Thanks for all your help!!  

Mike

"Mike" wrote:
[vbcol=seagreen]
> The CaseInformation Parent has no MinOccurs or MaxOccurs, but the child
> elements, Product and Reason, have a MinOccurs of 0 and a MaxOccurs of 1.
> Same with the DBConnection node.
>
> "Danny Buysse" wrote:
> 

[ Post a follow-up to this message ]