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

[Bug] Generated Dataverse delete() discards IOperationResult, so failed deletes are silent

Abierto
  • ¿Algo no está bien?
#469 1 comentario 0 reacciones 1 asignado Ver en GitHub

@ergonza93 ya está trabajando en esto.

Desde el 1/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

bug

Describe the bug

For Dataverse tables, the generated service's delete() method is typed Promise<void> and discards the IOperationResult<void> that client.deleteRecordAsync returns. deleteRecordAsync reports failure through success: false and error instead of throwing, so when Dataverse refuses a delete the failure is silently lost and callers cannot tell the delete did not happen.

create, update and get in the same generated file all return result, so only delete is inconsistent.

Generated code today:

public static async delete(id: string): Promise<void> {
  await Contoso_projectsService.client.deleteRecordAsync(
    Contoso_projectsService.dataSourceName,
    id);
}

The generator template is in @microsoft/power-apps-cli (the Dataverse service generator): the delete template emits await ...deleteRecordAsync(...) with no return, unlike the update template.

Steps to Reproduce

  1. Create a code app with Dataverse tables where a parent table has a Restrict-delete relationship to a child table (e.g. contoso_project -> contoso_task, with the child's lookup to the parent set to "Restrict" on delete).
  2. Add both tables with pa app add data-source --connector dataverse --table <name>.
  3. Create a parent row and a child row that references it.
  4. Call Contoso_projectsService.delete(parentId) from the app.
  5. Observe: the promise resolves normally, nothing is thrown, and the parent row still exists in Dataverse.

Expected behavior

delete should surface the failure the same way the other operations do: return Promise<IOperationResult<void>> (so callers can check success and error), or throw when success is false.

Actual behavior

delete resolves with undefined regardless of outcome. The error is discarded inside the generated wrapper, so UIs behave as if the delete succeeded.

Screenshots or Error Messages

None: the point of the bug is that no error is surfaced. Calling the client directly and checking the result does show the failure:

const result = await client.deleteRecordAsync('contoso_projects', id);
// result.success === false, result.error.message describes the blocked delete

Environment information

  • Framework, build tool or relevant package used: React 19, Vite 7, @microsoft/power-apps 1.2.12 (also type-checked against 1.5.0), @microsoft/power-apps-cli 0.15.2 (also inspected 1.2.0), @microsoft/power-apps-vite 1.0.2 (also 1.0.13)
  • Any connection/components: Dataverse (generated services via pa app add data-source / pa app refresh data-source)

Additional context

  • The behaviour was observed in an app generated with CLI 0.15.2 / runtime 1.2.12. I then regenerated with CLI 1.2.0 and read the generated output and the runtime 1.5.0 typings: delete is still Promise<void> and deleteRecordAsync is still typed Promise<IOperationResult<void>>, so it is not fixed in the latest versions I checked. I did not re-run the repro itself on 1.5.0.
  • Workaround: bypass the generated delete and call getClient(dataSourcesInfo).deleteRecordAsync(tableName, id) directly, throwing when result.success is false. Editing the generated file is not viable because it is overwritten on the next refresh.
  • Suggested fix: change the delete template in both the standard and partitionId variants to return the result, e.g. Promise<IOperationResult<void>> and return result;, matching update.
Lenguaje dominante
TypeScript
Estrellas
513
Forks
143
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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/PowerAppsCodeApps

Todos los issues de microsoft/PowerAppsCodeApps

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.