For long, we (as a partner community) have been asking for longer field lengths. And this time, Microsoft seems to have delivered: about 860 field lengths were changed. Mostly from Text50 to Text100... (Continue reading)

I’m returning back from yet another great Directions US event in Las Vegas this time. At this point – I’m sitting in the lounge in New York – a great opportunity to do a short post about something I didn... (Continue reading)

My intentional plan was to share a small blog about the Fall release of Business Central . Well – it turned out I had more to say than I imagined beforehand ;-).
I would like to focus on one point,... (Continue reading)

You might remember my blog from yesterday … . I didn’t know when it would be released.
Well, it wasn’t available yesterday, but today, I got the comment on my blog from Daniel Göhler that it was available... (Continue reading)

I’m not attending Directions ASIA this year – and it doesn’t really feel good. There is a major release around the corner, and I have to experience it through social media – I hate it! But that’s life... (Continue reading)

AL with VSCode: IntelliSense Fix

Since a recent update of VSCode, you might have noticed that IntelliSense works somewhat different. Well, that’s because VSCode thought to do a good, useful update for you .. but apparently for AL development, it turns out to be quite contra productive..

CTRL+Space

You all probably know why CTRL+Space is for? It’s for forcing IntelliSense. Or the official term is “Trigger Suggest“. In a context-aware intellisense, it’s very useful to get suggestions on which keywords can be used in a certain context.

Since one of the latest updates of VSCode, the default behaviour has somewhat changed. When you “trigger suggest” (press CTRL+Space), it will point to the last one used.

Like in this example, I use the snippet “tprocedure”, and when I use the CTRL+Space to start coding, you will see it will jump straight to the “tprocedure”-item in the list, just because I just used it:

In a context-aware in IntelliSense, this just doesn’t make any sense.

You can fix this

VSCode wouldn’t be VSCode if you couldn’t fix this behaviour. And I have a strong feeling you would like to fix it ;-). It’s simple, just add following setting in your settings.json (File / Preferences / Settings):

As the tooltip explains: Editor.suggestSelection controls how the suggestions are pre-selected when showing the suggest list. In this case it will always select the first suggestion.

This means it will always suggest the first item in the IntellSense-list. Just the way you would expect (in my opinion). Let’s see what this means for our example:

Thanks Esben & Stan

When I was doing my session in Bangkok last week, Esben and Stan saw me struggling with this, and gave me the solution. :-). Thanks so much!