PerTenantExtensionCop not flagging fields/enum values outside of app's defined id range

[tonyabriccomeske]

Please include the following with each issue:

1. Describe the bug
The PerTenantExtensionCop is not producing errors if you add a field or enum value outside of your apps extension range.

2. To Reproduce
Steps to reproduce the behavior:

1. Used AL:Go to create a new project. Downloaded symbols from Sandbox.
2. Used default app.json with an object range of 50100..50149
3. Added settings.json inside .vscode folder that enables the PerTenantExtensionCop

{
        "al.enableCodeAnalysis": true,
        "al.codeAnalyzers": [
            "${PerTenantExtensionCop}"
        ]
}

4. Created a table extension for the Customer table. Added a field with the ID 60000 which is inside the PTE range, but outside the range of IDs for this app.

tableextension 50100 CustomerTableExt extends Customer
{
    fields
    {
        field(60000; "Active"; Boolean)
        {
            Caption = 'Active';
            DataClassification = CustomerContent;
        }
    }
}

5. Build and deploy app to Sandbox. It publishes successfully, even though you have fields outside of your app range.

3. Expected behavior
When adding a field or enum value outside of your app's ID range, I would expect to receive an error (like you do when enabling the AppSourceCop).

Current Work Around - As someone developing a PTE, I wouldn't expect to need to leverage the AppSourceCop (and disable warnings) JUST so I can get effective warnings about developers on our team using fields and enums IDs outside of our app's range.

1. Add "${AppSourceCop}" to settings.json

{
        "al.enableCodeAnalysis": true,
        "al.codeAnalyzers": [
            "${PerTenantExtensionCop}",
            "${AppSourceCop}"
        ]
}

2. When you build, you are now getting AppSourceCop errors.
   The error that is helpful is the following:

error AS0013: The field identifier '60000' is not valid. It must be within the range '[50100..50149]', which is allocated to the application, and outside the range '[50000..99999]', which is allocated to per-tenant customizations.

I would like to see the first part of the error message be displayed when using the PerTenantExtensionCop

4. Actual behavior
A clear and concise description of what happened accompanied by images, animations, or a link to a video showing the issue occurring

This is problematic, as we could have multiple PTEs being installed, which in theory, we are expecting to maintain their own object range. If we do not receive any errors, you do not realize fields are added outside of the app range, and then it's a huge pain to clean up.

5. Versions:

• AL Language: 17.0.2273547
• Visual Studio Code: 1.133.0
• Business Central: US Business Central 28.3 (Platform 28.0.53152.0 + Application 28.3.52162.53387)
• List of Visual Studio Code extensions that you have installed: AL Language Extension
• Operating System:
  • Windows
  • Linux
  • MacOS

Final Checklist

Please remember to do the following:

• Search the issue repository to ensure you are reporting a new issue

• Reproduce the issue after disabling all extensions except the AL Language extension

• Simplify your code around the issue to better isolate the problem

[github-actions]

Good, environment is ready. Let me search for prior related issues and inspect the PerTenantExtensionCop rule source/docs, then attempt a real reproduction with the AL compiler and container.

Found the analyzer DLL and alc.exe. Now let's compile the minimal repro with PerTenantExtensionCop enabled.

Automated AL issue triage

Classification: feature request

Summary: Public documentation confirms PTE0002 ("Field ID must be in free range") intentionally validates only that field/enum-value IDs fall within the global per-tenant range 50,000–99,999, not within the app's own idRanges in app.json; the reporter is asking for a new capability equivalent to AppSourceCop's AS0013 own-range check to be added to PerTenantExtensionCop.

Environment

• AL Development Tools: 18.0.40.43394+64c78e364ff6f7fc1e34518914d5290296072bb5
• Business Central artifact: https://bcinsider-fvh2ekdjecfjd6gk.b02.azurefd.net/sandbox/29.0.53757.0/w1

Attempts and results

Attempt	Result	Evidence
Report completeness	complete	AL version (17.0.2273547), VS Code version, BC version, repro steps, inline AL code, expected vs. actual behavior all present.
Duplicate search	none found	Queries: repo:microsoft/AL PerTenantExtensionCop range (only this issue), repo:microsoft/AL field id range idRanges outside (0 results), repo:microsoft/AL PerTenantExtensionCop (14 results, no matching duplicate). No strong match.
Repository investigation	confirmed	Microsoft Learn PerTenantExtensionCop analyzer and PTE0002 docs state the rule validates field IDs against the fixed 50,000–99,999 range only, with no mention of the app's own idRanges. This matches the reporter's "actual behavior" exactly, indicating documented/by-design behavior rather than a defect.

Assessment

• Scope: out of scope - The request is for a new static-analysis capability (extending PerTenantExtensionCop to also check an app's own idRanges, not just the global free range), which references/scope.md classifies as a feature request/suggestion, not a developer-tooling defect, since the current behavior matches documented rule semantics.
• Confidence: high - Microsoft's own PTE0002 documentation explicitly describes the exact behavior the reporter observed as intentional.
• Likely component: PerTenantExtensionCop analyzer (Microsoft.Dynamics.Nav.PerTenantExtensionCop) - enhancement to rule PTE0002.

Recommended next step

Submit this as a suggestion via Business Central Ideas (https://aka.ms/bcideas) requesting that PerTenantExtensionCop optionally validate field/enum-value IDs against the app's own idRanges (similar to AppSourceCop's AS0013), since current behavior matches documented design rather than a compiler/analyzer defect.