# CamelCase named fields are missing in GraphQL explorer and introspection **URL:** \ **Category:** Developing with Prismic\ **Tags:** graphql\ **Created:** [December 7, 2020, 10:41am UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040 "2020-12-07T10:41:36Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![dmytrob](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@dmytrob](https://community.prismic.io/u/dmytrob)\ **Post date:** [December 7, 2020, 10:41am UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/1 "2020-12-07T10:41:37Z")
We are consistently experiencing the issue when fields defined in our content types, both in Slices and regular ones, are missing from GraphQL introspection result and GraphQL explorer. We tried publishing pages after changes, saving, resaving with no success. GraphQL is not very useful without the schema/introspection and this kind of inconsistent behavior makes GraphQL implementation not reliable. EDIT: After reading other topics I verified that missing fields are indeed using "camelCase". Is there any reasoning behind "camelCase" fields names not being supported in GraphQL and dropped silently? We have already a bunch of content published under the type, so we can't really change the field names. Are there any plans to address this issue? ---
**Author:** ![Fares](https://avatars.discourse-cdn.com/v4/letter/f/71e660/32.png) [@Fares](https://community.prismic.io/u/Fares)\ **Post date:** [December 7, 2020, 1:56pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/3 "2020-12-07T13:56:06Z")
Hi Dmytro, Thanks for contributing to the Prismic community. I will try to reproduce this issue on my side and it would be great if you can share with us an example of some fields that are being dropped. Also, it will be great if you can share with us your repository name (in a private message if necessary). Best, Fares ---
**Author:** ![Fares](https://avatars.discourse-cdn.com/v4/letter/f/71e660/32.png) [@Fares](https://community.prismic.io/u/Fares)\ **Post date:** [December 7, 2020, 2:39pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/4 "2020-12-07T14:39:16Z")
Thanks for your DM, I've asked the team about this. Meanwhile, we advise you to use _snake\_case_ instead. ---
**Author:** ![dmytrob](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@dmytrob](https://community.prismic.io/u/dmytrob)\ **Post date:** [February 23, 2021, 1:10pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/6 "2021-02-23T13:10:49Z")
Any updates on the issue? Kinda weird that the industry standard GraphQL naming convention is not only not encouraged, but completely broken! ---
**Author:** ![bippi](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/bippi/32/230_2.png) [@bippi](https://community.prismic.io/u/bippi)\ **Post date:** [March 18, 2021, 11:30am UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/8 "2021-03-18T11:30:23Z")
@Fares Do you know when GraphQL will be released from Beta. This fix is very important for my team. ---
**Author:** ![Fares](https://avatars.discourse-cdn.com/v4/letter/f/71e660/32.png) [@Fares](https://community.prismic.io/u/Fares)\ **Post date:** [April 20, 2021, 6:36pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/10 "2021-04-20T18:36:53Z")
Hello. We still don't have plans to update the current GraphQL functionality. We'll make a public announcement if we ever do. Thanks ---
**Author:** ![Fares](https://avatars.discourse-cdn.com/v4/letter/f/71e660/32.png) [@Fares](https://community.prismic.io/u/Fares)\ **Post date:** [April 20, 2021, 6:38pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/11 "2021-04-20T18:38:22Z")
---
**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/system/32/1746_2.png) [@system](https://community.prismic.io/u/system)\ **Post date:** [December 9, 2021, 4:21pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/12 "2021-12-09T16:21:24Z")
---
**Author:** ![newsroom](https://avatars.discourse-cdn.com/v4/letter/n/ecccb3/32.png) [@newsroom](https://community.prismic.io/u/newsroom)\ **Post date:** [January 11, 2022, 6:30pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/13 "2022-01-11T18:30:02Z")
Do you have an ETA for this? I experienced the same issue on my implementation, see image in the appendix. Mared in red (camelCase) is not working. Marked in green (all lowercase) is working camelCase named fields are not visible in GraqhiQL. It would be great to highlight this issue on the documentation, as I spent quite some time figuring out why its not working. Best regards, ![camelCase-uid-not-working](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/1/18571a8713d5dfc40aa1f20faa06888cf133c118.png) ---
**Author:** ![telco.pls](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/telco.pls/32/4579_2.png) [@telco.pls](https://community.prismic.io/u/telco.pls)\ **Post date:** [March 4, 2022, 2:49pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/18 "2022-03-04T14:49:20Z")
Hey, Do you guys have any solution for it? Because Slicemachine requires camelCase, but on graphql playground it doesn't work... ---
**Author:** ![Priyanka](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/priyanka/32/3223_2.png) [@Priyanka](https://community.prismic.io/u/Priyanka)\ **Post date:** [March 8, 2022, 11:13am UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/20 "2022-03-08T11:13:48Z")
Hello @telco.pls This fix is on hold for the moment. And I haven't any other solution unless sticking to the REST API. I apologize for that. Best, Priyanka ---
**Author:** ![peter2](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@peter2](https://community.prismic.io/u/peter2)\ **Post date:** [August 17, 2022, 12:38pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/22 "2022-08-17T12:38:49Z")
Is this issue just related to the GraphQL explorer or is this a generic issue of the GraphQL engine? I'm asking because Postman has built in support for GraphQL. I did perform some tests with Postman and was able to receive valid data, but I hit a couple of issues: Postman sends the query in the body and not as an encoded parameter. When I added the encoded query as a parameter, it worked. It sounds to be a much more sensible way than encoding a potentially huge json object and attaching that as a parameter. Does Prismic's GraphQL engine support queries to be send in the body? If yes, how? Postman uses POST to retrieve the schema. It uses the same header as the actual query and also puts the request into the body which might be the issue as per above, but I noticed that the error is different > {"message":"'\' not a valid key=value pair (missing equal-sign) in Authorization header: 'Bearer \'."} Can someone shed some light how to retrieve the Schema with Postman or is the Prismic GraphQL incompatible with Postman? Thanks Peter ---
**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\ **Post date:** [August 17, 2022, 6:16pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/24 "2022-08-17T18:16:48Z")
Hey @peter2, I'll reach out to the dev team about this. ---
**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\ **Post date:** [August 18, 2022, 9:48pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/25 "2022-08-18T21:48:51Z")
Hey @peter2, I'm don't think it'll work the same in postman. Because Prismic doesn't have a POST API. Here's a GraphQL introspection query to retrieve Prismic's GQL schema ```auto { __schema { types { kind name possibleTypes { name } } } } ``` ---
**Author:** ![gijs](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/gijs/32/4212_2.png) [@gijs](https://community.prismic.io/u/gijs)\ **Post date:** [December 14, 2022, 2:32pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/27 "2022-12-14T14:32:33Z")
@Priyanka @Pau Could you guys please fix this? I'm running into maximum depth issues with graphQuery on the rest client, and wanted to bypass that with the GQL client. But, I created all my fields and 90% of my types with camelCase names. I'm now stuck because I can't fetch the documents and fields I need. Please fix this. ---
**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\ **Post date:** [December 15, 2022, 12:15am UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/29 "2022-12-15T00:15:52Z")
Hey @gijs, we don't have plans to update the current behavior of the GraphQL endpoint naming conventions. You can still query the fields with their API IDs without the Camel Case: `exampleTitle` would appear in the schema as `exampletitle`. I understand this might not be ideal for the developer experience, but it is the quickest workaround, instead of having to rename all fields. ---
**Author:** ![aarnipavlidi](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/aarnipavlidi/32/5757_2.png) [@aarnipavlidi](https://community.prismic.io/u/aarnipavlidi)\ **Post date:** [April 3, 2023, 3:32pm UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/31 "2023-04-03T15:32:03Z")
Wondered myself also few days, that why I had trouble to fetch data from graphql if type field was named with camelCase. ![Screenshot 2023-04-03 at 18.25.25](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/9/9d568e8c32b626aee5a599d19af9c6d12c113888.png) ![Screenshot 2023-04-03 at 18.25.17](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/1/16c7fe6d929c23000fdb5267f92da5b113c08892.png) Is there any possibility to revisit this and possibly make a change? Because to me it feels "wierd" to name for example following field as: homelandingpage, instead of naming it "homeLandingPage". Ofc I could just ignore this and make it as "home\_landing\_page" as for better readability. Also when I started using Prismic for first time, and was playing around with default Prismic client for fetching data, there is no issue pulling data with camelCase, which gave me illusion that I could pull data the same way from GraphQL, which was not the case. This is a worth thing to mention at documentation as a suggestion! 🙂 ---
**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\ **Post date:** [April 4, 2023, 3:36am UTC](https://community.prismic.io/t/camelcase-named-fields-are-missing-in-graphql-explorer-and-introspection/3040/33 "2023-04-04T03:36:47Z")
Hey @aarnipavlidi, there is no news to change this at the moment. But I'll share your comments with the Education team so they can see how to make this clearer in the documentation. Thanks for sharing your case and feedback.