I suggest you...

Enhance the subscription filters

The subscription filters are key to BizTalk’s functionality, yet the filter rules and structure has not developed. We need:
- A “Not exists” operator
- Deeper grouping of filters, i.e. don’t limit to only one level of grouping
- A “Contains” operator would also be welcome

The use of “Not exists” and “Contains” would increase the value of the filters, at a minimal cost to processing time.

The value of content based routing is limited when you can only do one level of grouping. For example, the following logical filter:
(Source == JCD AND (TypeID == 52 OR TypeID == 61 OR TypeID == 74))
Or
(Source == BCG AND (TypeID == 75 OR TypeID = 76 OR TypeID = 80))

has to be implemented as:
(TypeID == 52 And Source == JCD)
Or
(TypeID == 61 And Source == JCD)
Or
(TypeID == 74 And Source == JCD)
Or
(TypeID == 75 And Source == BCG)
Or
(TypeID == 76 And Source == BCG)
Or
(TypeID == 80 And Source == BCG)

19 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Nabeel PriorNabeel Prior shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • MarkMark commented  ·   ·  Flag as inappropriate

        If you need something more complex than the filter functionality can provide - or it's awkward, as in your example - I guess you are expected to do the logic in an orchestration and promote a flag that can be used in the filter.

      • FernandoFernando commented  ·   ·  Flag as inappropriate

        One thing missing that should always have existed is the LIKE operator. This would help a lot.

      Feedback and Knowledge Base