Biztalkien

Leonid Ganeline - Microsoft BizTalk Server & WCF

  Home  |   Contact  |   Syndication    |   Login
  62 Posts | 0 Stories | 76 Comments | 13 Trackbacks

News





free counters

Archives

Post Categories

Image Galleries

BizTalk

Interesting information in KB:
"How to use distinguished fields and promoted properties in a BizTalk Server project" http://support.microsoft.com/kb/942250
 
"...
  • A promoted property may not be available as a promoted property after you write a value into the message context. This situation can occur if the value that you write into the message context has the same name and namespace that was used to promote the property.
  • Properties that have a null value are not permitted in the message context. Therefore, if a null value is written into the message context, this value will be deleted.
    ..."
 
BTW What is it "a null value"?
  • Is it <shipDate xsi:nil="true"></shipDate> ?
  • Is it absence of the value <shipDate></shipDate> ?
  • Is it "closed tag <shipDate /> ?
  • Is it absence of the whole node?
 
In http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/#Nils we have description of it. But frequently we've got different interpretation of this term. And I am not sure about interpretation in KB
 
 
And let me add one more, not obvious:
  • Distinguished fields and promoted properties have to always get Min/Max Occurs = 1. (Not 0, not "unbounded", only 1)
posted on Wednesday, July 09, 2008 8:51 AM

Feedback

# re: BizTalk: Distinguished fields and Promoted properties - additional information 9/21/2008 10:25 AM Tom Canter
Null actually means setting the context property to null.
For instance, in an orchestration:
MyMessage(My.MessageProperty) = null;
This will delete the property... when the property is sent out to the message box (Send Port) the property is deleted from the message context.

If you want to preserve a promoted property then make it a following correlation on the send port.

I wrote up some useful information about Distinguished and Promoted fields that may shed some light on the subject.
http://blogs.neudesic.com/blogs/enterprise_integration/archive/2007/10/16/18739.aspx

Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification: