Hi there,
We are facing problems querying records that are cached but have never been accessed by the user while online. Currently, we are using GraphQL to retrieve the data.
While offline, all records are accessible through the native "Offline Records" page. However, they are not accessible through the custom LWC, which uses GraphQL.
What should we do to retrieve these cached (briefcase downloaded) and previously not accessed records using an LWC?
--
Steps to reproduce:
Step 1
There is a custom object with three related records synchronized and accessible while offline. Those records were opened in the past while online.
Step 2
Create a new related record on the desktop. Record RDM-80865 is created under its parent EDM-16645.
Step 3
Synchronize the records on mobile. Records primed.
Step 4
Turn off the connection and open the Parent Record (EDM-16645) through the LWC. The related records list does not load. Why?
Step 5
While offline, the newly created record is accessible only through the Offline Records List (Briefcase).
Doing that, users lose all the navigability benefits that a Lightning Web Component brings. In addition, it is challenging to search for records only using their auto-number naming.
--
@Irfan Syed @Adam Liechty @Yaswant Sappaa
Thanks for the reply @Yuri Garcia Caetano. I think that answers my first question. However, I'm curious about my #2 and #3 questions: What does the GraphQL query wire emit in cases of a record that was not previously accessed? Your function wired to your graphQL query should be called with an object: {data, errors}. I'm assuming in the case the related list fails to show, 'data' is not defined when your function is called back, but 'errors' has some info about what went wrong, which will hopefully point us in the right direction.
