PTE0004 raised when publishing on cloud environments without reason

[nicolassaleron]

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

5. Add the table in the permissionset and do not fully qualify the table: use a using directive instead.
6. 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

[BB97GER]

We are currently experiencing the same issue.

The workaround described here also worked for us: removing the namespace and the corresponding using statement from the permission file allowed us to deploy the PTE again. Nicolas Saleron (@nicolassaleron) Thx . for the Workaround!

Interestingly, we have seen similar behavior occasionally in the past. In those cases, the first deployment failed, but simply retrying the deployment a second or sometimes a third time succeeded — without making any changes to the app in between.

However, since September 29, deployments for one of our PTEs have consistently failed and retrying no longer helps. Removing the namespace and the corresponding using statement was the only workaround that allowed us to deploy it again.

It does not seem to be a general issue with namespaces in permission files, though. We have another PTE where namespaces and using statements are still present in the permission file, and deployments of that app continue to work without any problems.

Version: DE Business Central 28.4 (Platform 28.0.54688.0 + Application 28.4.53241.54676)