BizTalk map functoid vs BizTalk map xslt -

i using biztalk map , inside biztalk map using table looping, table extractor, scripting, looping functoids.

the same can achieved in biztalk map referencing xslt.

so performance wise, method better using biztalk map or biztalk map referencing xslt.

in fact, visual biztalk map created biztalk mapper, xslt. functoids libraries/functions may either xslt or inline c# code. 1 way can check right click .btm map , click 'validate'. in output window, see link xslt file.

performance tricky xslt. can write xslt in way or in way it's not meant used. pretty basic mapping, performance differences there, pretty minor (if @ all). dijkgraaf says: way check this, test it.

if current implementation gives performance issues, try writing purely xslt, optimized either way. try taking different approaches/techniques.

in general, recommend writing xslt instead of using mapper, let's honest: personal preference. wrote blog post on this, check out here: https://pvandenheede.wordpress.com/2016/09/20/the-case-for-xslt/