,

Troubleshooting AL Extension in VS Code: Phantom Errors

When working on an AL Extension, you may encounter a phantom error where a table appears in red, indicating a missing permission set despite successful compilation. This can occur due to dependency updates. To resolve it, close and reopen VS Code or restart the Extension Host, prompting verification of dependencies and permissions.

Marcel Chabot
1–2 minutes
, , , , ,

So, you are working on an AL Extension, you’ve added a few tables, and added those tables to at least one Permission set file. However, the table is still marked in Red, and it is complaining that the table is missing a matching permission set.

Everything compiles fine, so this is some kind of phantom error.

You might see something similar if you update the dependencies. The issue is that some of the files and associated errors are only handled when the AL Extension starts.

To resolve this issue, you could close and reopen VS Code, or you could press CTRL SHIFT P and select “Developer: Restart Extension Host”

This will restart the AL Extension, and it will verify the dependencies and permissions files.

This is the good old IT 101, turn it off and back on again.

One response to “Troubleshooting AL Extension in VS Code: Phantom Errors”

  1. Osvaldo B. Rossi Avatar
    Osvaldo B. Rossi

    Great tip!
    You can also use Developer: reload window to also refresh the code files, in case you’re using an AI agent that modifies the files.

    Like

    Reply

Leave a comment

Trending