Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
747
stars
245
forks
source link
CurrFieldNo in OnAfterInsert not set when set from TestPage (was #5400) #6945
That link is the top search result on Google and Bing for "Business Central" CurrFieldNo... not a good look to have that outdated info, instead of an updated page for BC screaming THIS DOES NOT WORK ANYMORE...
We have decided to only fix your second issue, since the first one is by design. If you invoke validate from the client, the `CurrFieldNo is updated, but if you invoke it from code, it isn't.
Anyway... I'll file a doc bug for that.
Back to AL itself - surely there should be an exception for Test data types, as they should emulate what will really happen in the client...?
but I have tested, so you don't have to, and the code in #5400 clearly does not.
Please advise. Thanks!
versions:
GB Business Central 19.2 (Platform 19.0.32956.34593 + Application 19.2.32968.34839)
Name: AL Language
Id: ms-dynamics-smb.al
Description: AL development tools for Dynamics 365 Business Central
Version: 8.3.570094
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-dynamics-smb.al
https://github.com/microsoft/AL/issues/5400 is still an issue.
Through having written a bunch of code using it, I have determined that I wasted my time, as in BC
CurrFieldNo
does not work how it used to in NAV, as documented in: https://docs.microsoft.com/en-us/dynamics-nav/xrec-and-currfieldnoThat link is the top search result on Google and Bing for
"Business Central" CurrFieldNo
... not a good look to have that outdated info, instead of an updated page for BC screaming THIS DOES NOT WORK ANYMORE...It was written here: https://github.com/microsoft/AL/issues/4152#issuecomment-440182277
Anyway... I'll file a doc bug for that.
Back to AL itself - surely there should be an exception for Test data types, as they should emulate what will really happen in the client...?
but I have tested, so you don't have to, and the code in #5400 clearly does not.
Please advise. Thanks!
versions: