Exception returns unique error number which can be cross-checked with ServiceCenter Error Log

By Gonçalo Veiga on 14 Nov 2010
The same way there is a Session.ExceptionMessage, there should be a Session.ExceptionNumber.
All error records would be uniquely identified by this number.
This could be shown to the end-user, and could be vehicled back to the adminstrator, or support team, or to be recorded in an ECT.
This capability would help production troubleshooting.
This is indeed very useful in case of an Error analysis / 'drilldown'.

It would also be nice if we could isolate errors that occur during a given session based on the session ID (or user id).
Since the session ID IS already logged, this shouldn't be hard to implement.