I did not understand your question ?
Your error is displayed when you visit the contract types collection. I want to see the request and the response of the http request.
Do you speak french ? Maybe we can switch to french language to better understand each other.
Bonjour, oui biensûr nous pouvons passer en Français.
Souhaitez-vous dâautres informations ?
Les informations que vous me donnez ne sont pas suffisantes, il me faut une trace dâune erreur. Nous nâavons pas accĂšs Ă votre serveur. Sans ça je ne pourrais pas vous aider.
Dans le dernier screenshot que vous mâavez envoyĂ©, ĂȘtes-vous sĂ»r quâil nây a aucune erreur ? Y a-t-il une ligne route dans la liste ? (vous pouvez dĂ©rouler la liste vers le bas, pour voir toutes les requĂȘtes).
Nous nâavons aucune erreur sur le serveur.
Certains documents sont accessibles et dâautres non.
Quand on duplicate la ligne, il retrouve bien les datas.
Quand on veut accĂ©der Ă ces lignes, on obtient lâerreur reach data. Pas dâerreur dans les logs.
Hey Vincent
(Switching back to english so other users can benefit from this)
This thread seems quite long so Iâll try to sum it up:
- Some of your records display a âCannot reach your dataâ error.
- When duplicating these records, you do not experience any issues.
- All http endpoints send back HTTP 200 Response.
My best guess would be that there is an issue with a specific response. Usually, this error can be displayed whenever the response doesnât contain specific informations.
In order to help, iâll need exactly the following informations:
- Payload and response for the
/contract_type
call
These can be retrieved by:
- Opening the chrome developer console
- Switching to the network tabs
- Searching for the specific call that retrieve a single record (You should be able to directly search
contract
in the search bar visible on the screenshot. - Sending the whole payload & response as text (You can send those via private message)
Once Iâve got this information, I should be able to understand what is going on - and to provide a solution or a workaround to fit your use-case.
Thanks in advance
After deeper investigation in private message, it appeared to be a discrepancy between the data in mongodb & in the model definition:
- Model contained a definition for a âBelongsToâ equivalent for a specific fields (Letâs call it
foo
) - Some mongo records contained
foo: <an Id>
, some other containedfoo: [<An array of ids>]
.
This led to âCannot reach your dataâ error when the loaded record didnât match the model structure, saved in the forestadmin-schema.
Fixing the issue was then mostly a matter of fixing the model.
Thanks for your help debugging this, Iâll mark this thread as resolved