Skip to main content
RiyaSh10
Aug 8, 2025 12:17 PM UTC
Solved

In AEM We are not getting value "@type" from Content Fragment to Graphiql

In AEM We are not getting value "@type" from Content Fragment to Graphiql

We have a Jsontype Field in content Fragement where I am passing SEO Script 

but apart from "@type" I am getting all values from CF to Graphiql

Shiv_Prakash_Patel
Shiv_Prakash_PatelAccepted solution
Community Advisor
Aug 8, 2025 3:21 PM UTC

@14236791 is a JSON-LD reserved key, and many Java/GraphQL pipelines (including AEM’s GraphQL JSON scalar/Jackson stack) treat keys starting with @ as unsafe (they’re used in polymorphic deserialization exploits). So AEM’s GraphQL layer drops or ignores @14236791 while passing the rest (name, url, image, etc.). That’s why you see everything except @14236791 in GraphiQL.

Shiv Prakash
View in thread

3 replies

Shiv_Prakash_Patel
Community Advisor
Shiv_Prakash_PatelCommunity AdvisorAccepted solution
Community Advisor
Aug 8, 2025 3:21 PM UTC

@14236791 is a JSON-LD reserved key, and many Java/GraphQL pipelines (including AEM’s GraphQL JSON scalar/Jackson stack) treat keys starting with @ as unsafe (they’re used in polymorphic deserialization exploits). So AEM’s GraphQL layer drops or ignores @14236791 while passing the rest (name, url, image, etc.). That’s why you see everything except @14236791 in GraphiQL.

Translate
Shiv Prakash
    HrishikeshKagne
    Community Advisor
    HrishikeshKagneCommunity Advisor
    Community Advisor
    Aug 8, 2025 3:45 PM UTC

    Hi @riyash10 ,

    Rename the field in your Content Fragment model to something like type (without @). Then, in your frontend, map it back to @type when rendering the JSON-LD for SEO.
    seoData["@type"] = seoData["type"];
    This avoids GraphQL limitations while still delivering valid structured data.

     

     

    Thanks!

    Translate
    Hrishikesh Kagane
      Tanneru
      Tanneru
      Level 2
      Aug 10, 2025 5:08 PM UTC

      When you're not getting the @14236791 property from an AEM Content Fragment (CF) in GraphiQL, but you're getting other properties, the issue is most likely due to the fact that @ is a reserved character in GraphQL and/or JSON serialization contexts. AEM and GraphQL might be stripping or ignoring the property name starting with @.

      Translate
        Terms & ConditionsAccessibility statement

        Loading footer...