System.Exception catch

(0) Share

Report

Posted on by D365FO user

465

Hi,

I thought system.Exception catches everything

So i had the following

Catch(Exception:Error)

{

Here i return what is saved in sysInfoLog

}

Catch(ex) //this is system.Eception

{

Info(ex.Message)

}

Catch{ i also return what is inside sysInfoLog}

Now what happened is, during inserting into logisiticsPostalAddressEntity.. An error occured that says countryRegionId should be filled

If there was no catch for the system exception, then the general catch will return this missage for me.(not sure why this wasn't catched by the error catch??? )

However when i added the system.Exception catch, the debug entered this catch. However it returned nothing.

Does that mean that inside the ex catch, i should check if ex.Message==null then check the sysInfolog? But why it returned nothing?

I have the same question (0)

All responses (3)

Answers (0)

huijij 19,811 on at

Like (0)

Report
Copy link

Link copied!

Hi sir,

A direct throw of Exception::Error does not display a message in the Infolog. And the Global::error method is recommended.

https://docs.microsoft.com/en-us/dynamicsax-2012/developer/exception-handling-with-try-and-catch-keywords#sample-2-error-method-to-write-exception-to-infolog

regards

Was this reply helpful? Yes No
D365FO user 465 on at

Like (0)

Report
Copy link

Link copied!

Hi Judy,

Thanks for that. But i'm not throwing errors, I'm catching them

And my question was about system.Exception..it seems i should not print in the catch ex.Message i should check if it's null as well to display sysInfolog message because it seems sometimes ex.message is empty even though the debug entered the catch

Was this reply helpful? Yes No
Martin Dráb 239,040 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Please use the debugger to check the type and properties of the exception. Then share the information with us.

By the way, please always use Insert > Insert Code to paste source code here. It makes code easier to read, e.g. it prevents the double line spacing. This is your code posted in the right way (I also fixed letter case at a few places):

catch (Exception:Error) { ... } catch (ex) // this is System.Exception { info(ex.Message) }

Was this reply helpful? Yes No