fn:lower-case does not work in 6.1 if we are using querybuilder? is this a known issue? | Community
Skip to main content
New Participant
March 3, 2016
Solved

fn:lower-case does not work in 6.1 if we are using querybuilder? is this a known issue?

  • March 3, 2016
  • 7 replies
  • 2272 views

WE r running a query were we are doing something like:

group.1_property=fn:lower-case(/jcr:content/metadata/@documentTitle)

 

This doesn't work. is this a known issue?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

 we never officially supported functions.  Hence not a bug. You have to file enhancement request to support xpath function. 

7 replies

New Participant
March 3, 2016

Thanks a ton

Lokesh_Shivalingaiah
New Participant
March 3, 2016

From AEM 6.x, recommended approach to use SQL2 or JQOM for queries 

You can refer JQOM example here : http://adobeaemclub.com/jcr-java-query-object-model-jqom-adobe-aem-query/

New Participant
March 3, 2016

Kunal, thanks. We are planning the same. Curious thing is it does work in 5.6.1

New Participant
March 3, 2016

Sham,

It does work in 5.6.1 though. When you say not officially supported, just for my information, is there a document we can refer to what's supported? So if it's not supported, isn't it a part of sling or AEM isn't supporting it.

Confused as to who you mean doesn't support. Where does the predicate implementation exist for this function?

Sham_HC
Sham_HCAccepted solution
New Participant
March 3, 2016

 we never officially supported functions.  Hence not a bug. You have to file enhancement request to support xpath function. 

Kunal_Gaba_
New Participant
March 3, 2016

We encountered the same issue with lower case function when we upgraded to 6.1. We raised a daycare ticket with Adobe support and they did mention that it is a known issue with the OAK repository. We then converted the query to SQL2 version in our code as a workaround to fix the issue.  I am not sure may be they might have fixed it in 6.1 SP1. 

smacdonald2008
New Participant
March 3, 2016

I will send this to support to see if this is a known issue.