Sorry Iām not sure about what you are doing on the website, are you launching the same GraphQL query? Itās strange that you get two different results
Well the custom data field is there on API explorer but empty when retrieving from gatsby graphlq (using gatsby-source-datocms), and yes Iām using the same query for both of them.
The problem with Gatsby is that you are not using our GraphQL endpoint directly. They are reconstructing a GraphQL-like data structure that you can interrogate locally, but the information is coming from our REST API.
I can confirm that the data is not exposed in our source plugin, Iām going to open an internal task for this and report back when there are news!
Hey @rinor, we found the bug! It was only on āMultiple assetā fields, thanks for reporting! Version 2.5.17 of gatsby-source-datocms should fix the issue, let us know!
Hey @s.verna, after I updated the gatsby-source-datocms to 2.5.17, and then trying to run it locally it getās stuck while creating pages, URL path: /privacy_infra/ Context: { "id": "DatoCmsPage-******-en" } [== ] 15.687 s 57/545 10% run page querie