Here is another strong point of HAT...
Today while browsing through HAT documentation I found an interesting/powerful function of HAT:
Menu "Reporting" -> "Find Message"
It's not the first time I see this functionality, but I really never stopped to think about it. Today I needed to find one "lost" orchestration, I knew the day and hour I should look for it in HAT, and using a custom query with a where clause:
datepart(hh, sf.[ServiceInstance/StartTime])
datepart(month, sf.[ServiceInstance/StartTime])
datepart(day, sf.[ServiceInstance/StartTime])
(datepart documentation)
I was able to narrow a time frame with a certain number of orchestration, well just happens that this certain number is a big number of orchestrations.
I stopped to think a while about this problem, so I found the hidden power of "Find Message". With this functionality I only had to promote a certain field in my schema and with this promoted field I'm now able to track my "lost" orchestration.
I will leave a link to some problems with this functionality:
Tracking Promoted Properties and using them in HAT
