Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

PTE0004 raised when publishing on cloud environments without reason

Abierto
  • ¿Algo no está bien?
#8,346 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
50/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Área
cloud, compilers

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
PowerShell
Estrellas
884
Forks
285
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/AL

Todos los issues de microsoft/AL

Issues similares

Más issues de Cloud

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.