|
Home > Archive > BizTalk Server General > September 2005 > Filter Expression Property List Problem
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 |
Filter Expression Property List Problem
|
|
|
| Hi,
I have a solution containing 3 projects:
Project 1: Contains a Property Schema 'PS'
Project 2: Contains a Document Schema 'DS' with elements Promoted using
'PS'. It references Project 1.
Project 3: Contains an orchestration beginning with an activate receive. It
references Projects 1 and 2.
Within the Receive shape in Project 3, the properties of PS are not shown,
so I can't build a Filter expression. However, if I move 'PS' from Project 1
to Project 2, and then re-promote 'DS', I can then see the Promoted
properties within the Filter Expression list. Once I have built my Filter
expression, I then move 'PS' back to Project 1, re-promote 'DS' and deploy
the projects.
Does anyone know why I can't see the promoted properties in the Filter
Expression list when 'DS' is not in the same project as 'PS'? This is really
confusing me.
Many thanks!
Glynn
| |
|
| Nobody on this newsgroup was able to help me with this problem, so I opened a
case with Microsoft. They confirmed it to be a bug, the details are attached
below. However, my workaround was slightly different. I moved the property
schema temporarily into the same project as the document schemas, created the
filter expression and then moved them back again.
You will also notice that the expression editor does not show intellisense
for the promoted properties, and the same workaround fixes this problem too.
Hope this info is useful to anyone else who experiences this problem.
Microsoft confirmed there is no hot fix for the problem, just workarounds.
Their synopsis is shown below:
Symptoms
=============================
When trying to access a promoted property in an expression or in a Receive
Shape Filter, the property may not be shown.
Cause
=============================
This can occur if the property schema is in a referenced project rather than
in the project containing the schema used.
Repro Steps
=============================
Create 2 BizTalk projects.
In Project 1, create a property schema with a field.
In Project 2, add a reference to Project 1
In Project 2, create a schema with an element and promote that element using
the property schema from Project 1
In Project 2, Add an orchestration and a receive shape. Mark the receive
shape as an Activate receive and then attempt to add a filter.
Look in the list for the promoted property. It's missing.
More Information / Workaround
=============================
If the schema and property schema both come from the same assembly, all
should be well. The issue here is that the property schema exists in a
separate assembly from the schema which uses it. When designing BizTalk
solutions, Orchestrations should be kept in a separate assembly from schemas
anyway, therefore, putting the schemas and their associated property schemas
together and then referencing that assembly from the orchestration project
will allow the property to be displayed in intellisense.
|
|
|
|
|