OK, I had enabled message and property tracking on the ****t, but I hadn't
enabled tracking of the property within the specific schema. So I went and
did that. Then I ran another message through the system. Then I went to
Find
Message and there are still no properties in the drop down list. Is there
something else I have to do for the changes I just made to take effect?
Earlier responses to this thread from Mihai Dan said that I had to have
the
job that copies data from the management database to the tracking database
running. Is that true. I thought that HAT would query the live management
database. And if I run my query with just date range filtering, without
any
property specification, it finds the messages. I just can't find a message
by a promoted property.
"Jan Eliasen" <eliasen@[EMAIL PROTECTED]
> wrote in message
news:g7u5t3pmlvcb22qg9lmn8qh05jrlk5o6ju@[EMAIL PROTECTED]
> On Thu, 6 Mar 2008 08:53:38 -0500, "Zoe Hart"
> <zoe.hart@[EMAIL PROTECTED]
> wrote:
>
>>I'm trying to figure out what I have to set where to get the HAT Find
>>Message feature to work. On my orchestration I enabled tracking for
>>message
>>properties. But when I go to HAT Find Message and choose a schema for a
>>message sent to my orchestration with a promoted property, the Property
>>drop
>>down list in the Message properties filter section of the window has no
>>properties in it. What do I have to enable where to get my promoted
>>properties to show up in that list? Should I be enabling tracking of
>>message
>>properties in the appropriate send or receive ****t in addition to or
>>instead
>>of in the orchestration? Is there something other than enabling tracking
>>of
>>message properties that I need to do? Are the promoted properties
supposed
>>to show up in this list? For me the list of properties is always empty.
I
>>want to be able to find messages for a specific order number and most of
>>my
>>messages have order number as a promoted property.
> Try this:
>
>
http://blog.eliasen.dk/PermaLink,guid,f4306b11-74b0-41f5-93e9-224d84405af0.aspx
>
> --
> eliasen, representing himself and not the company he works for.
>
> Private blog: http://blog.eliasen.dk
>
> Private email: jan@[EMAIL PROTECTED]
|
