|
Home > Archive > BizTalk Server Orchestration > October 2004 > Distinguished Field not available in Orchestration. Why?
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 not available in Orchestration. Why?
|
|
| Lars W. Andersen 2004-10-15, 9:09 pm |
| Hello,
Maybe a stupid question but here it comes anyway ...
Why am I (sometimes) not able to access a distinguished field in my
orchestrations?
I take an old solution that only used messaging and "wrap" the schemas and
maps in an orchestration.
So I use an already existing schema, remove the property schema and the
already promoted properties. I save all and then go back and promote the
properties as distinguished fields, as I no longer need them in my ports.
BUT ... I can't access the distinguished fields in my orchestration. If I
add a new schema "test" and promote a field as "test", I can access THAT
disting. property right away. But it doesnt seem to work on my existing
schemas.
I CAN get to my promoted properties with the
"ReceiveCheck(DM_NetLine_Technical_Check.Schemas.PromotedName)" syntax. But
I like the Distinguished field solution better.
If only I could get it to work.
To confuse me further: I another old solution where the fields where
promoted as both distinguished and property fields, I can get to the
Disting. fields right away.
So I am scratching my head here ... what am I missing?
regards
Lars
| |
| Matt Milner 2004-10-15, 9:09 pm |
| Did you undeploy the property schema for the old solution? If you have the
old solution deployed, then the promoted properties are still deployed.
Because distinguished properties do not go into the property schema, you are
running into the problem of an overlap.
If you have undeployed, and redeployed this property schema without this
property, then make sure you restart your biztalk services to see the
changes.
Matt
"Lars W. Andersen" <lwa@maerskdata_nospamplease_.dk> wrote in message
news:e78y2iFsEHA.1036@TK2MSFTNGP10.phx.gbl...
> Hello,
>
> Maybe a stupid question but here it comes anyway ...
>
> Why am I (sometimes) not able to access a distinguished field in my
> orchestrations?
>
> I take an old solution that only used messaging and "wrap" the schemas and
> maps in an orchestration.
> So I use an already existing schema, remove the property schema and the
> already promoted properties. I save all and then go back and promote the
> properties as distinguished fields, as I no longer need them in my ports.
>
> BUT ... I can't access the distinguished fields in my orchestration. If I
> add a new schema "test" and promote a field as "test", I can access THAT
> disting. property right away. But it doesnt seem to work on my existing
> schemas.
>
> I CAN get to my promoted properties with the
> "ReceiveCheck(DM_NetLine_Technical_Check.Schemas.PromotedName)" syntax.
> But
> I like the Distinguished field solution better.
> If only I could get it to work.
>
> To confuse me further: I another old solution where the fields where
> promoted as both distinguished and property fields, I can get to the
> Disting. fields right away.
>
> So I am scratching my head here ... what am I missing?
>
> regards
> Lars
>
>
| |
| Lars W. Andersen 2004-10-15, 9:09 pm |
| Hi Matt, I see it now. Thanks for the tip. Just what I needed.
regards
Lars
"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:OSEyYYGsEHA.1752@TK2MSFTNGP14.phx.gbl...
> Did you undeploy the property schema for the old solution? If you have
the
> old solution deployed, then the promoted properties are still deployed.
> Because distinguished properties do not go into the property schema, you
are
> running into the problem of an overlap.
>
> If you have undeployed, and redeployed this property schema without this
> property, then make sure you restart your biztalk services to see the
> changes.
>
> Matt
>
>
> "Lars W. Andersen" <lwa@maerskdata_nospamplease_.dk> wrote in message
> news:e78y2iFsEHA.1036@TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
ports.[vbcol=seagreen]
I[vbcol=seagreen]
>
>
|
|
|
|
|