Debug::assert statements found in Sys layer in Dynamics Ax 2009
This morning I was surprised to see Debug::assert statements in Sys layer table object as I was traversing the InventTrans tree node.
[Sorry for wrongly pressing the panic button… 😉 This seems to be pretty common with new versions of Ax. Please see comments from Kashperuk]
If you look at \Data Dictionary\Tables\InventTrans\Methods\unpostedInvoiceIdForReceivedPurchType method then you will find more then 5 assert statements in it. I quickly checked where this method is being used from. It was called from a display method inside the same table. Luckily one of our developer have commented it during rollup upgrade. This statement can attempt to open the debugger if the assertion is false. So I guess it would be good if you would do something to prevent it.
Hope anybody from Microsoft following this blog would take it further to fix it…..
Share this:
Leave a Reply
Dynamics Ax News
- 12 Key Takeaways Microsoft Dynamics 365 Finance & AX Users ... - MSDynamicsWorld12 Key Takeaways Microsoft Dynamics 365 Finance & AX Users ... MSDynamicsWorld
- DynamicsCon Virtual 2023 & Microsoft Customer Success Day ... - MSDynamicsWorldDynamicsCon Virtual 2023 & Microsoft Customer Success Day ... MSDynamicsWorld
- Event Preview: Defining a successful Dynamics AX to Dynamics 365 ... - MSDynamicsWorldEvent Preview: Defining a successful Dynamics AX to Dynamics 365 ... MSDynamicsWorld
- Financial Tags in Microsoft Dynamics 365 Finance: A long-awaited ... - MSDynamicsWorldFinancial Tags in Microsoft Dynamics 365 Finance: A long-awaited ... MSDynamicsWorld
- Introducing Microsoft Supply Chain Platform - Microsoft Dynamics ... - MicrosoftIntroducing Microsoft Supply Chain Platform - Microsoft Dynamics ... Microsoft
- Microsoft boosts Viva Sales with new GPT seller experience ... - MicrosoftMicrosoft boosts Viva Sales with new GPT seller experience ... Microsoft
Visitors Info
Ax Community
On the Web
Ax blogs stream
- An error has occurred; the feed is probably down. Try again later.
Casperkamal's Dynamics Ax blog 
Maybe it is common in AX 2009. But anyway it is no good idea to do it.
Debug.assert() will invoke the call stack and pause further execution of code if there is a debugger.
The problem is the words PAUSE and IF THERE IS A DEBUGGER
In production environment you don’t have a debugger and therefore debug.assert() will do nothing and code execution is going on.
So if there is something VERY wrong, you are now in problems. Your process in production will maybe fail somewhere later in the code with a runtime eror. And you don’t know why, cause you missed the nice condition tested in debug assert.
There is a nice article about it: http://www.sharplogic.com/blogs/ed/PermaLink,guid,976a0613-da9b-433e-b909-07d37ce407b2.aspx
———- Comments From Kashperuk in axforum.info —————————–
Actually, you’ll see a lot more of those in the new AX release.
There is nothing wrong with putting such statements into the code.
Their purpose is to assert a very specific condition, that MUST be satisfied.
If it is not, something is VERY wrong, and we should not continue.
They are intended for developers changing the code – when doing some testing of the changes, you would be able to easily see that something is wrong.
So, again – this is a good thing that they are there.
———————————————————–