Mapper Property Promotion

Here is a little something that I did not realize was happening when BizTalk executes a transform. If you have a property schema associated with the destination schema in a map, BizTalk will automatically promote those properties when it executes the map. This does not help if you need to promote an adapter context property or another property schema that is not associated with the destination schema. For those you will still need to use another tactic like promoting properties using an initializing correlation set.

Generally I promote properties for the adapters or a generic envelope schema and I just recently observed this behavior. If you are working on a project that uses promoted context properties to route messages this may be an easy way to set those values.

.net activemq adapters akka amazon amqp apache api appfabric architecture authentication azure biztalk bpm caching camel cep cloud cloud computing cqrs data formats design eai edi esb esb toolkit events governance hateoas html http hypermedia integration java jax-rs jms json linked data links linux mapping masstransit media types messaging microdata monitoring msmq mule node.js nservicebus oauth odata open source orchestration patterns powershell pubsub python queues rabbitmq rdf rdfa resources rest resteasy routing rpc ruby security semantic web service bus services sesame signalr soa soap sparql spring streaminsight testing topics transactions transformation uri versioning videos wcf wcf data services wcf web api web web api web services websockets wf windows workflow xml xsd zeromq