Hi @touseefk2181136 ,Seems as per you use case below code should work. From frontend just pass shopName and address and made changes in servlet as below. package com.yourproject.core.servlets;//change as per you code baseimport com.day.cq.search.PredicateGroup;import com.day.cq.search.Query;import c...

Hi @touseefk2181136    PFA, You may easily extract the shop id from path(string operation- split) of search result. Even we can use shopName as well shopAddress to check if present by grouping property in query.path=/content/data/shopproperty=shopNameproperty.value=name2 OR path=/content/data/shopgr...

Hi @touseefk2181136 ,You may use ajax call /content/data/shops.infinity.json as suggested by @h_kataria  OR you may use below approach. From front-end just pass shopName and shopAddress only in shopData object to Servlet always.Then in servlet itself first check if that shop name exist by fetching(m...

Hi all, If someone stumbled to this error in future then the error is not related to any steps which missed. This issue is same as https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/dispatcher-on-windows-throws-error-default-was-unexpected-at/td-p/456498Most probably can be fi...

Hi all,This error is more related to dispatcher tool's batch file as this file has issue with some windows  version & some machine.So instead of wasting time in docker version or AEM we should debug batch file based on error we get.We can use echo command intuitively for debug purpose and  add/remov...

Hi @RahulMohan ,There can be following two scenario.Find all images which are missing some property field in the metadata(that property might be custom or added later so some asset might not have those fields(property) in metadata nodeFor this scenario above reply (in this thread)perfectly match and...

Hi @RahulMohan ,Please find the below query for finding the asset which are not having a specified metadata properties. type=dam:Assetpath=/content/dam/your-project-folder-name1_property.operation:exists1_property=jcr:content/metadata/dam:ColorSpace1_property.value:falsep.limit=-1 Above query will f...

Hi @Johann_Lu ,You can open error.log file in some editor which support these Chinese text instead of using AEM log console.These text are not readable in AEM console but same file's text is readable in other application/editor.PFA for reference.AEM console log:-Same error.log file in Text editor:-(...

Hi @kvarthi ,Though whatever you have done is correct but there can be another approach which might be better depends on yours use case.You may provide a drop downs of all the variant in dialog if most of the fields are same. Based on the variant you can render html with the help of sightly.Even if ...