Business Rule Composer problem!

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Business Rule Composer problem!

Viewing 1 reply thread
  • Author
    Posts
    • May 31, 2006 at 3:16 PM #13750
      community-content

        Hi.
        I have an irritating problem with the BRE 👿
        My problem is that my xml message doesn’t update correct after the BRE.

        Basically what I am doing is
        1. Call the BRE from an orchestration.
        2. The call rule shape adds the xml message A to the BRE.
        3. Inside the BRE I connect to a SQL database and get an int value (using the built in connection under facts).
        4. If the value from the database is bigger then two the xml element (bool) in message A is updated to “true”
        That’s it

        And now the problem:
        The xml message A is not getting updated.
        If I test the policy inside the BRE the value of the xml message is updated correctly.
        If I change the condition to always true (inside BRE) the xml message A is correctly updated when using the orchestration.
        What have I done wrong???

        This is getting me really frustrated, so has anybody any id%u00e9e what to do?

        Please help me!

      • May 31, 2006 at 6:32 PM #13751
        community-content

          Thanks for the reply Stephen W. Thomas!

          I have tested my input from the orchestration with a basic test:

          My XML message is built up by 2 attributes, one Boolean and one integer.
          I have changed the rule so it compares the integer value of the xml message with 2. If true the boolean is switch to true.
          This works fine when called from the orchestration.

          But if the integer value is delivered from the database, the xml message will not change when called from the orchestration.

          Strange

          • May 31, 2006 at 3:33 PM #13752
            community-content

              Are you sure the message you are passing into the BRE has the values you are expecting?

              Maybe something is not set as you expect so your rule isn’t firing or your SQL isn’t working right.

              It sounds like you are doing everything right. If it works outside the Orchestration and when the rule is always true it sounds like a problem with the input.

              • May 31, 2006 at 10:37 PM #13753
                community-content

                  Maybe it’s a type problem. i.e. database isn’t returning a 2 but many 2.0 or something.
                  Maybe you could wrap the db return value

                  One rather easy thing to try is create a simple .net component that takes in your two values (the db value and your 2). Then, you can convert them so you know they are the same and do your comparison.

                  Just make sure you pass in a reference to the .net component at a fact and make sure to GAC it.

                  Best of luck.

          • Author
            Posts
          Viewing 1 reply thread
          • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.