I know that we can use POST method to make normal GQL query and perform GQL Ops but I wanted to know how can we achieve the same for persisted query, when I make a POST call with variables, I get an error:   When I copy URL which takes variables AEM gives URL which looks like this: https://<DOMAIN>...

I want to implement atleast one filter provided by AEM on an array field to filter the categories which contains atleast one of the values:   _expressions: [ { _apply: AT_LEAST_ONCE, values: [ "health", "fitness" ] } ]   Now...

I want to query the tag names. Here's my query to get tags:   type=cq:tagpath=/content/cq:tags/rallyp.hits=selectivep.properties=jcr:path jcr:title.es jcr:title name   However this doesn't return the tag to me:   I also tried to use jcr:name, nodename, and jcr:nodename but none of that seem to work...

@LUKA  Can you elaborate a bit more on /bin/tagcommand?

I wanted to know if it would be possible to create AEM tags and namespaces programatically using Assets API in AEM?

Is it possible to configure content fragment models so that they generate unique dynamic file IDs when creating content fragments which could be used for querying purposes and all?

I am new to adding translations in AEM. Very likely we would be using Transperfect. Has anyone used it before? Can we roll out translations programatically in variations instead of having separate copies in other folders?

I was looking into QueryBuilder API when I saw the ability to do advanced configuration:   http://localhost:4503/system/console/configMgr/com.day.cq.search.impl.builder.QueryBuilderImpl   Now I saw a lot of technical terms there and not sure about what exactly do they mean and how can I tweak them ...

I am using GQL API to fetch data from AEM. However I need to have logic like contains or doesn't contains in `_path`. I wanted to know if the same is supported in AEM through GQL APIs? Like for example I see CONTAINS, CONTAINS_NOT for other fields but not for the _path. For the path, I only see EQUA...

Got it sorted by performing variation as filter, instead of variation query { articlesList(variation:"spanish",filter:{ _variation: { _expressions: [ { value: "spanish", _operator: EQUALS, _ignoreCase: true } ] } }) { items { ...