microsoft / microsoft/AL

altpgen.exe (AL Table Proxy Generator) missing from extension bin folder in v18.0.2726309

Open
#8,337 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted packaging
Dominant language
PowerShell
Stars
881
Forks
285
Avg merge
3d 36m
Merged PRs (30d)
1

Description

The AL Table Proxy Generator tool (altpgen.exe) is documented as being installed with the AL Language extension at \bin\altpgen.exe (see AL Table Proxy Generator docs). In previous versions (e.g. 17.0.2273547) it shipped at bin\win32\altpgen.exe.

In the current version (18.0.2726309), the extension's bin folder has been restructured ΓÇö the old win32/linux/darwin platform subfolders are gone and tools sit directly under bin (alc.exe, altool.exe, aldoc.exe, almcp.exe, etc.). However, altpgen.exe is not present anywhere in the extension folder at all ΓÇö not under bin, not under any subfolder. I confirmed with a full recursive search of the extension directory.

I also checked altool.exe's command list (altool --help) and it has no equivalent subcommand for CDS/Dataverse proxy table generation, so the functionality doesn't appear to have been folded into altool either.

This means there's currently no way to generate AL proxy/integration tables for Microsoft Dataverse (CDS) tables using the AL Language extension, despite the official documentation still describing this workflow as supported.

Steps to reproduce
Install AL Language extension version 18.0.2726309 (or later) in VS Code.
Look for altpgen.exe under \bin\ (or any subfolder).
Observe the file does not exist.
Expected behavior
altpgen.exe should be present in the extension's bin folder as documented, or the docs/changelog should indicate a replacement tool/command for generating Dataverse proxy tables.

Actual behavior
altpgen.exe is completely absent from the extension package.

Environment
AL Language extension version: 18.0.2726309
VS Code version: 1.137.0
OS: Windows 11 Enterprise (10.0.26100)
Internal work item: AB#649813

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the AL Language extension package's bin directory for version 18.0.2726309 and compare it with the documented installation path and the earlier bin\win32 layout. Run altool --help to confirm there is no replacement command; done means restoring altpgen.exe or documenting a supported replacement in the extension or documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.