AEM GraphQL failing on properties with custom namespaces. How to query properties with custom namespaces?

[saravanaprakash]

For our project, we created a new namespace `salsify:` under Content Fragment. For example,

salsify:size
salsify:class
salsify:color

When creating PersistedQuery, the GraphiQL editor converts colon (:) to underscore and the queries are failing. 

For example, above, property names are actually `salsify:size`, `salsify:class`, `salsify:color`. But graphql editor converts colon to underscores. Now when filtering for input parameters, the query always returns empty items. 

I tried CONTAINS, EQUALS, doesn't work. 

We cant query properties with namespace using graphQL?

[TarunKumar]

HI @saravanaprakash ,

graphQL schema naming convention allows only camelCase, PascalCase or SCREAMING_SNAKE_CASE fields. Colons are not allowed in graphql fields.
AEM replace any special characters to underscores. So salsify:size becomes salsify_size for the AEM schema.

Solution:-
Try to append _ignoreCode:true to the filter. This is not required for normal properties but only for name space

Thanks
Tarun

[Kamal_Kishor]

@saravanaprakash : You can refer this article if you are still having issues - https://medium.com/@bsaravanaprakash/how-to-filter-properties-with-custom-namespaces-in-aem-graphql-...

thanks.

[kautuk_sahni]

@saravanaprakash Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.