GraphQL refresh not calling wire adaptor when used after updateRecord()

Abierto
#369 0 comentarios 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
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
graphql, typescript
Área
devtools

Línea de trabajo

Start with the Local Dev server's GraphQL wire-adaptor refresh path and reproduce the sequence using updateRecord followed by refreshGraphQL. Confirm the behavior with a deployed LWC and the listed CLI environment; done means the wire adaptor executes and exposes the updated record after updateRecord.

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

Descripción

Summary

In this LWC I am developing, a user has a list of records. They can add new records or go to another page to edit one of these records. When the user updates the record and they navigate back to the list and then view the record again it still displays the old value.

For the insert and update of these records I am using the LWC createRecord and updateRecord from the uiRecordApi. For fetching the data I am only using GraphQL queries. Viewing new data after a record is inserted works fine but fails to update after an update.

From the Network tab, a call is made to update the record and then a second call is made to execute the GraphQL but the wire adaptor is never called. This only occurs when using a Local Dev server, when developing without it the data refreshes correctly.

A comment on this StackExchange post is also having the same issue.
https://salesforce.stackexchange.com/questions/421684/refresh-graphql-is-not-working-in-lwc

Steps To Reproduce:
  1. Start a Local Dev server
  2. Create a LWC with a GraphQL wire adaptor
  3. Use the updateRecord method to update one of the records retrieved from the GraphQL query
  4. Call the refreshGraphQL method on the wire adaptor result
  5. Make sure you have deployed your changes as changes have been made that are related to wire adaptors
Expected Result

The wire adaptor for the GraphQL query is executed.

Actual Result

The wire adaptor for the GraphQL query is not executed and the updated record is not available to be used.

Additional Information

Screenshots:

Image

System Information

SF CLI:

shell: powershell

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.78.3",
  "nodeVersion": "node-v22.13.1",
  "osVersion": "Windows_NT 10.0.26100",
  "rootPath": "C:\\Users\\myUsername\\AppData\\Local\\sf\\client\\2.78.3-b3024dd",
  "shell": "powershell",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.21 (core)",
    "@oclif/plugin-commands 4.1.20 (core)",
    "@oclif/plugin-help 6.2.25 (core)",
    "@oclif/plugin-not-found 3.2.40 (core)",
    "@oclif/plugin-plugins 5.4.32 (core)",
    "@oclif/plugin-search 1.2.21 (core)",
    "@oclif/plugin-update 4.6.31 (core)",
    "@oclif/plugin-version 2.2.23 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.33 (core)",
    "@oclif/plugin-which 3.2.29 (core)",
    "@salesforce/cli 2.78.3 (core)",
    "apex 3.6.8 (core)",
    "api 1.3.3 (core)",
    "auth 3.6.94 (core)",
    "data 4.0.11 (core)",
    "deploy-retrieve 3.20.0 (core)",
    "info 3.4.39 (core)",
    "lightning-dev 2.10.3 (user) published 13 days ago (Tue Mar 04 2025)",
    "limits 3.3.46 (core)",
    "marketplace 1.3.7 (core)",
    "org 5.2.32 (core)",
    "packaging 2.9.17 (core)",
    "schema 3.3.50 (core)",
    "settings 2.4.16 (core)",
    "sobject 1.4.50 (core)",
    "telemetry 3.6.33 (core)",
    "templates 56.3.38 (core)",
    "trust 3.7.65 (core)",
    "user 3.6.9 (core)"
  ]
}

OS:

Windows 11 (Version 10.0.26100 Build 26100)

Lenguaje dominante
TypeScript
Estrellas
19
Forks
19
Merge medio
3 d 12 h
PR fusionados (30 d)
2

Guía de contribución

Abrir la guía de contribución

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 salesforcecli/plugin-lightning-dev

Todos los issues de salesforcecli/plugin-lightning-dev

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.