'server' method throwing error needs to be 'caught' for more meaningful message.

(0) Share

Report

Posted on by b_radlyjames

3,061

Here is what I'm trying to do.

I am calling code which eventually leads us to Classes\DimensionDefaultingEngine\constructForMainAccountId method. This method will throw the following error correctly:

if (!_mainAccountId || !_accountStructureId)
{
throw error(Error::wrongUseOfFunction(funcName()));
}

The account structure for the main account is not setup correctly. This is perfectly fine. The error should be thrown.

What I want to do is 'catch' this thrown error so that I can give the user a more meaningful message to have them fix the problem.

try { ...}

catch (Exception::error){

error("Meaningful message");

}

This try / catch doesn't seem to want to do anything.

*This post is locked for comments

All responses (2)

Answers (1)

b_radlyjames 3,061 on at

Like (0)

Report

RE: 'server' method throwing error needs to be 'caught' for more meaningful message.

Thanks Joris! This was exactly it.
Verified answer

Joris dG 17,775 on at

Like (0)

Report

RE: 'server' method throwing error needs to be 'caught' for more meaningful message.

try-catch in AX has specific behaviors based on transaction scope. The code where you placed the try catch is likely being called from within a transaction scope, which means you essentially can't catch it.

Check this out: daxmusings.codecrib.com/.../exception-handling-in-dynamics-ax.html