- This topic has 4 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Hello.
The first time I use distuiginshed fields. And now I find out that I can build it in two ways.
a) Click on the node in the schema and choose promotion -> quick promotion, click “ok”. Then a new schema called “PropertySchema” comes up. I closed it and go back to my first schema. I right clicked on the node “schema” and choose “show promotions”. After this I can put the promoted field to the distuingished field.
b) The other version of building distuingished fields is to click in the first schema on the schema node and go to the properties. In the “Promoted Properties” field I can click on (Collection) and the window for the Promote Properties appears. Now I can choose which field should be a distuingished field. No new schema was build this way.
My questions are:
Which way I have to go to get access to the distuingished field in an orchestration?
Do I have to use the new PropertySchema in the orchestration?
What is the difference between version a) and b)?
Thank you very much in advance.
Wolfgang
-
Hi Wal,
Quick promotion – makes promotion to fields, with creating property schema.
Distinguished fields – can be used in orchestration only, and you can access to them with intellisence in Orchestration shapes. MessageOfYourSchemaType.DistinguishedField = value;
Using property schema – enables you to set values in context in pipeline, or pass context of a message by context to other parts of your solution., or using correlation for exapmple.
Right click – quick promotion is same as right clik – show promotions – property fields etc.
Distinguished field after promotion, sets some data into schema, and quick promotion on the first field creates property schema if you don’t have it, and if you do – it adds field name to property schema.
-
Hi Yonathan.
Thanks for your explanations, this helps a lot.
One further question, do I have to use a property schema if I like to use these distuingished fields in an orchestration?
In my scenario b) I can build distuingished field without the help of a property schema. So I don’t know at the moment if I have to use a property schema.
Thanks
Wolfgang
-
Hi Wolfgang, your’e welcome.
If you use only distinguished fildes – you don’t need any property schema.
If you will need at any moment to promote some properties, let’s say in custom component for incoming message, in custom piepline, you can create property schema, and choose fields you want to promote. In current project for example, we use some fields of messages as distinguished (to get some values with this sintax: “value = message.FieldValue”; ), and some values we get from incoming message, and promote it to context for routing of messages afterwards.
So, it’s up to your decision and architecture.
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.