BizTalk mapper 2010 – determine issues with custom functoids

 

In case the mapper fails (and only then, these steps will help you out a bit!) when you do Test map, and it seems to be caused by a Custom Functoid that can not be loaded, perform the following steps;

image

You have to call the ‘Debug’ map, this will generate the XSLT and will start the debugging

image

This will give you an error in case there are errors

image

Look in the output window, for the clear and distinct hint Bedroefde emoticon (e.g. : NS0 is the namespace causing the problem);

image

Now perform a ‘Validate’ map to get the Extension XSLT;

image

Open the .extxml.xml

image

Look for the specific namespace (NS0):

image

Open the custom functoid and make sure that the classname / SetExternalFunctoin are EXACTLY identical.

image

image

If this is the case, you can do the following (but you’re problably in the zone….the problem zone)

1) Perform a build on the Functoid library

2) Redeploy the Functoid library

3) Restart visual studio

4) Open the map, Reset the toolbox

5) Verify that the map works

LAST RESORT!!

6) Remove the Custom functoid, and add the functoid

 

HTH,

 

Sander

Comments

Popular posts from this blog

Azure implementation guidelines

Focus and innovation - recap of the last 2 years

BizTalk Pub/sub vs Topics based routing–discussion