Hi @dopamine7, in my opinion you should not call servlet from your sling model - I think this is not a good practice. Instead if you need to run some operation from servlet and sling model you can extract your logic into separate class i.e. OSGi service and use it in all other classes. This should e...

@user00928, I have run the code on my local instance and it looks to be working fine. It seems that you've set your debugger break-point on class level - which is too early. The new object of the class is not initialized yet. What you could try, is to set your break-point on some method inside your ...

Hi @user00928, could you please try below implementation @Model(adaptables = { Resource.class }, defaultInjectionStrategy = DefaultInjectionStrategy.OPTIONAL) public class Navigation { @Inject private List<PrimaryLink> primaryLinks; @Model(adaptables = Resource.class, defaultIn...

Hi @reverieit09, you need to contact Adobe to get the price - you can use this site to contact Adobe sales team https://business.adobe.com/products/experience-manager/sites/pricing.html

Hi @naveen123, so summarizing, it was working fine on AEM 6.3 with ACS Commons 3.19.0, now you are on AEM 6.5.8 and using ACS Commons 4.12.0. Did you try to remove all you customization form AEM instance and see if this will help? Or increase logging level - to get some more details related to repor...

What version of AEM are you using? Do you have any service pack installed? How did you upgrade ACS commons - I mean did you just installed 4.12.0 version on top o 3.19.0, or you have removed 3.19.0? Last question did you try to remove any customization form your AEM instance e.g application that you...

Thanks, the configuration looks fine, did you try to run any other reports? I am wondering if the issue is related only to your report or it is more generic and affect entire Report Builder functionality.

Could you please share how queryconfig node looks like?

Hi @naveen123, it looks that you are using Report Builder from ACS Commons. The reason of above error could be incorrect configuration of Query Language value that can be configured as part of JCR Query Report Configuration component. In that case I would suggest to verify what value has been config...

Hi @Sanjay_Bangar, do you have your dispatcher flush agent on publish enabled? According to this docs https://helpx.adobe.com/experience-manager/kb/optimizing-the-dispatcher-cache.html#use-ttls dispatcher flush agent should be disabled on publish.