11
When entering asserterror in code and using a record variable after, the record variable is missing intellisense. See https://github.com/microsoft/AL/issues/5915 for more details and a short video.
Although it is best practice in TDD to call procedures instead of statements as much as possible, the usage of statements is supported, sometimes it's simply easier/sufficient, it is documented to be used with statements (*), and thus should be considered by intellisense.
(*)
see https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-testing-application#asserterror-keyword
"The AssertError keyword specifies that an error is expected at run time in the statement that follows the AssertError keyword."
Although it is best practice in TDD to call procedures instead of statements as much as possible, the usage of statements is supported, sometimes it's simply easier/sufficient, it is documented to be used with statements (*), and thus should be considered by intellisense.
(*)
see https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-testing-application#asserterror-keyword
"The AssertError keyword specifies that an error is expected at run time in the statement that follows the AssertError keyword."
STATUS DETAILS
Needs Votes
Comments
The issue was originally raised for record variables, but intellisense is GENERALLY broken after it:
Using intellisense after asserterror, you even cannot call helper functions.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.
Best regards,
Business Central Team