Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

PTE0004 raised when publishing on cloud environments without reason

Open
  • Is something wrong?
#8,346 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
50/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
cloud, compilers

Research direction

Start by reproducing the issue in a cloud sandbox with the namespace and using-directive examples from the report, then compare publishing with VSCode or AL-Go, where it does not occur. Done means the same permission set publishes without PTE0004 when the referenced table is resolved through a using directive.

Written by the indexing model from the issue text.

Description

1. Describe the bug

This bug has been signaled first on Viva Engage.

I am experiencing an issue and was wondering whether other partners have encountered the same behavior.

My observations are as follows:

When deploying a PTE in a BC FR environment (Platform 28.0.52495.0 + Application 28.3.52162.52579), in my case by manually uploading the .app file, the deployment fails with the error below if:

  • the permission set is defined inside a namespace, and
  • the object referenced in the permission set is resolved through a using directive.

Package validation failed due to the following error(s): (5,13): error PTE0004: Table 80000 '***' is missing a matching permission set. (5,13): error PTE0004: Table 80001 '***' is missing a matching permission set. (7,13): error PTE0004: Table 80003 '***' is missing a matching permission set. - Job Id : e581f2c1-b75d-46da-8dc8-4abbcb2362fb

As soon as I remove the using directives and fully qualify the object names in the permission set, the deployment succeeds.

2. To Reproduce
Steps to reproduce the behavior:

  1. Create an AL PTE app with one table and one permissionset (with no namespace)
  2. Publish it to a cloud sandbox
  3. Add a namespace to the table: MyApp.Tables
  4. Add a namespace to the permissionset: MyApp.PermissionSet

It seems important that both objects are in different namespaces

  1. Add the table in the permissionset and do not fully qualify the table: use a using directive instead.
  2. Publish it to a cloud sandbox... sometimes you will get this error.
namespace MyApp.PermissionSet;

using MyApp.Tables;

permissionset 80000 "MyApp Permissions"
{
    Assignable = true;
    Caption = 'MyApp Permissions';
    Permissions = tabledata "MyApp Table" = RIMD,
      table "MyApp Table" = X;
}

namespace MyApp.Tables;

table 80000 "MyApp Table"
{
   fields
   {
      field(1; "PK"; Integer) { }
   }
}

3. Expected behavior
PTE0004 should not be raised.

4. Actual behavior
PTE0004 is raised even if the table is part of a permissionset.

5. Versions:
This issue does not occur when compiling on VSCode or with AL-Go. It only occurs when publishing on a cloud environment.

It has been reproduced on the following platform/application versions:

  • On July, 17th 2026: Platform 28.0.52495.0 + Application 28.3.52162.52579
  • On September, 30th 2026: Platform 28.0.54846.0 + Application 28.5.54151.55108
Dominant language
PowerShell
Stars
884
Forks
285
No merged PRs in 30d

Getting set up

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.

More from microsoft/AL

All issues in microsoft/AL

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.