You’re offline. This is a read only version of the page.
107
Hi guys,
In standard Ax code, i've seen Debug:Assert() statements regularly, but today we experienced some very odd behavior.
When posting a Free Text Invoice, at some point we hit the method "exchRateCurToMst" in table CustTrans. In this method, a Debug:Assert is triggered.
We run the posting of the Free Text Invoice in batch, and we noticed that the batch would just stop, no error, and the Free Text Invoice was not posted.
When debugging in Visual Studio, we noticed that the Debug:Assert code causes this behavior.
Has anyone seen this before?
The solution i've found on the internet suggests placing all Debug::Assert() calls in comment, but i was hoping there was a "cleaner" way of doing this.
*This post is locked for comments
I have the same question (0)
Hi,
One Question: Is the behaviour the same if 'debugging' is generally disbaled on the box?
Debug Asserts sometimes behave different and very strange if debug is enabled.
I would not prefer simply commenting out this. Because there must be some sense behind this(hopefully). Some kind of "we have a siutuation which shouldn't be there (and maybe leads to wrong data if we go on)"
regards
Douglas
Share
Report
All responses (
Answers (
