maps - Promoted Property in Orchestration -

i have reading can promote property in orchestration. below steps -

1. create new "studentid" promoted property.
2. change value "messagecontextpropertybase".
3. update value of "studentid" in orchestration.
4. create new correlation set of "studentid".
5. initializing correlation set of send shape.
6. create send port in biztalk administrator console.
7. set filter "poc.promotedproinox.schema.propertyschema.studentid == "7" "

i getting no error. want if "studentid" 7 should subscribe.

issue - think it's not checking value of "studentid" message file drop in out folder.

am missing something?

there several things missing

1. if message on receive port has message has same promoted property correct studentid of 7, both orchestration , send port subscribe it. if set studentid else in orchestration message sending through send port didn't go through orchestration came directly receive port.
   fix: have value received message set else or not have promoted property on inbound message.

2. you have specified logical port in orchestration specify later , bound send port. default send port has subscription of it's unique id. when orchestration publishes message through logical port bound send port sets , promotes id when publishes message. adding subscription rule means treat bts.spid = {id} or {your rule}. means if studentid not match subscription rule on send port match spid , still pick up.
   fix: change logical port in orchestration direct bound.

3. the third possibility orchestration message publishing in fact have studentid of 7.
   fix: check construct shapes (map & assignment) make sure setting value. make sure message specified in send shape 1 constructed new value.

the way analyze problem @ context properties of message going through send port, either enabling tracking of properties before pipeline, or stopping (but not unenlisting) send port , looking @ context properties of suspended message(s).

if message going through send port has studentid = 7 either have done #3 or #1 see below.

if message has details of receive port studentid, has come directly receive port per #1. expect see error orchestration when attempted publish message different studentid, unless either orchestration did not run (look @ tracked instances) or see below.

if message going through send port has promoted property of bts.spid logical port bound send port per #2.

if getting 2 messages each 1 put in, have 1 of each of above , have done both #1 & #2.

in summary, check context properties of message whenever not route way expect too.