Bug Scenario: You are using C# variable in Mapping Functoids.
You run a map through “Test Map” and it works fine each time.

You run a file through a receive location, running the same map. Works great first time, but second time it maps nothing (or behaves differently). When you restart BizTalk Host Instance, it works fine first time, but not second time.

Why are we using a variable in the first place? The ideas was to map a field just one time (in a loop). So once the field is mapped, we need to set a flag not to map it again.


What is the bug in the following code?

<code>
public static bool gotCoborrowerLastname = false;

public static string CoborrowerLastname (string param1)
{
     string result = "false";
     if (param1.ToUpper() == "TRUE" && !gotCoborrowerLastname)
         {
                gotCoborrowerLastname = true;
            	result = "true";
         }

      return result;
}
</code>

The “static” keyword must be removed from the global variable. By making it static, only one copy of the variable is held in memory. Thus, the variable stays set to the last value, even when you run a new map. The variable does not get reset until you restart the BizTalk Host instance.

<code>
public bool gotCoborrowerLastname = false;
</code>

Tagged with:

Filed under: Maps