A recent discussion on the community forum about exception messages prompted me to test the given case thoroughly and I think the results are worth sharing. The post also mentions something what I already found before – that error handling can be tricky in code which uses .NET Interop and which can be executed as both X++ and CIL.
Let’s introduce the problem. We have an X++ class method (AX2012) that throws an exception:
public class XppClass
{
public static void run (...(read more)![]()
↧