Hi,
this is my query,
path=/content/dam
type=dam:Asset
1_group.property=jcr:content/metadata/productdata/itemStatus
1_group.property.1_value=D
1_group.property.2_value=X
2_group.property=jcr:content/metadata/productdata/samsExpirationDate
2_group.property.operation=exists
3_group.daterange.property=jcr:content/metadata/productdata/samsExpirationDate
3_group.daterange.upperBound=2025-08-28
3_group.daterange.operation=<
p.limit=-1
p.offset=0
p.guessTotal=true
when I use the full property path for daterange which is under productdata not returning results. when I give property as 'jcr:content/metadata/*/samsExpirationDate' it's working and returning the results.
productdata node and property:
also property is added in the latest oak:index.
what could be the reason?
Thanks
Views
Replies
Total Likes
Even I thought same. but for few assets samExpirationDate property type is Date. Still no results.
Views
Replies
Total Likes
Hi @arunpatidar , after removing the property from the oak:index then the query is working.
<samsExpirationDate
jcr:primaryType="nt:unstructured"
name="jcr:content/metadata/productdata/samsExpirationDate"
propertyIndex="{Boolean}true"/>
I have added the property in oak like this. Also it's not just this property. any date property inside productdata is behaving same when filtering using daterange.
@Keerthana_H_N just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies