Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

CQ Asset share customization for sorting

Avatar

Level 2

Hi All,

 

We want ability to add sorting mechanism for CQ Asset share page which will enable users to sort the assets listed on the page based on different attributes.

Any pointer on how to do this will be really appreciated.

 

Thanks and Regards,

Nitin

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

By default it uses data view lens which wont provide any sorting functionality.

option 1: Refer damadmin or siteadmin pages.

option 2: Use third party jquery libraries kie table sorter. 

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

By default it uses data view lens which wont provide any sorting functionality.

option 1: Refer damadmin or siteadmin pages.

option 2: Use third party jquery libraries kie table sorter. 

Avatar

Level 10

You can sort assets stored in the JCR based on different props. For example, you could write an OSGi component that queries assets, sorts them based on a specific property, and then return a reset set to the page where they are displayed. Everything in CQ is just a resource. You can get at that resource using an API like JCR SQL/JCR API and sort it.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----