Today, at work, we may have found a risky (since it involves referential integrity) NAV 2016 platform bug. Here’s what I thought I knew about the NotBlank property – see if you agree:
Just like any piece of software, there are some bugs in NAV account schedules, and the best way to deal with them is to know they exist. I’ll let the Microsoft folks debate whether these are a bug or not. To me, as an end-user, anything that removes a necessary feature or keeps a necessary feature from operating reliably without replacing it with something better is a bug.
My colleague Mathias Meissner found a strange bug in the Dynamics NAV Client (occurs at least in the native clients for NAV 403, 501 and 601). It seems the following code creates a strange memory allocation issue.