@Ravi_Pampana  The strange part is that i am able to work with the list successfully on my local but not on higher env. The .json (url exposed as JSON) works fine as well. It is the rendering of the list components on the page that throws a 500 Error. Will try checking for special characters but a s...

Totally, that is what makes me wonder, I see a Null pointer Exception but very unclear and version 4.10.0 acs commons. It does not appear to be special char issueERROR- GET /mnt/overlay/acs-commons/components/utilities/genericlist.html-    org.apache.sling.engine.impl.SlingRequestProcessorImpl servi...

All, Is there a limit to the number of items in an ACS Commons generic list . The page just appears blank and a 500 error is thrown. Limiting to 6 entries or 4 helps. Anyway i can get around the issue? I am on aem 6.5.8 

Not yet Pallavi, but I am determined to do so since we have majority users using assets and search .. 

I have below in my filter file. The oak:index/content.xml file has entries for damassetlucene index as well with custom properties.    

@DEBAL_DAS  have you tried the approach of not including custom index into oak index? I somehow missed this and I think it’s a good idea to keep it away from oak index

Hi , as stated the index html checked in for two indices that weren’t sling folder had no namespace. Adding this new index with sling folder created troubles, since the namespace was missing this is the cause that is fixed thanks all and you @DEBAL_DAS  ,.. you’ve been pretty helpful most of the tim...

Thanks @Anish-Sinha , i agree will take the pipeline approach, will revert if any issues. 

Thank you so much will be doing that

Hi  Vijayalakshmi, I was working on omnisearch and i had an index which unfortunately did not have sling:prefix in its header and it had the damlucene index in the filter as update, so it created troubles. I tried reindexing and (possibly deleting via build can't recollect).But now it is in the repo...