AL Object ID Ninja
Zero-configuration, dead-simple, lightning fast, no-collision object ID assignment for multi-user repositories
- No collisions, ever: Real-time, conflict-free ID assignment that always gives every developer a guaranteed unique object ID.
- Lightning-fast: Get your conflict-free object IDs instantly, with IntelliSense integration.
- Zero-configuration: No setup, no onboarding, no settings — you work exactly like before, and it silently keeps your IDs clean.
From the blog
Getting the exception type from the GETLASTERROROBJECT
In my last post I have introduced the GETLASTERROROBJECT function that returns you the instance of the System.Exception class, representing the actual exception that has happened.
To properly handle exceptions in an unambiguous way, you must use the exception type, not its name, so it is important to get the actual System.Type representing the exception type.
Sounds easy, but it’s not quite so.
Better error handling in NAV 2015
You may love C/AL as a language, but there is an area in it that you must just hate. It’s the error handling. Plainly put, and being actually quite positive about it, in NAV, error handling just sucks. If an error happens, it happens. You have only one possibility to actually capture the error, and it’s the IF CODEUNIT.RUN construct, and it’s limited because you can do it only once per transaction, and if you want to do it twice, you must COMMIT your transaction first.
But still, capturing an error is one thing; actually handling it is quite a different thing altogether.
Directions EMEA 2014 content
- Go to the previous page
- 1
- …
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- …
- 161
- Go to the next page
