Hi Team,
After migration into CoralUI Query is not generating, while it was working before migration.
Please find below XML file and help me out:-
<generateQuery
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/button"
icon="icon-info-sign"
name="./generateQuery"
granite:rel="tagFilterQuery"
text="Generate Query"/>
<queryField
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/textarea"
granite:class="queryTextArea"
disabled="{Boolean}true"
fieldLabel="Generated Query"
name="./queryField"
rows="3"/>
Please help me out !! Thanks in advance
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @rajnishkr93
Compare the logic/markup of Resource (sling:resourceType of dialog fields) used for source element Button (Generate Query) and the target element (textarea) prior to and after Migration.
On a very high level, it could be the identifiers (class/id or HTML tag name) or if you are relying on custom properties on a dialog field node.
Share the complete dialog resources used and custom JS for debugging further.
Hi @rajnishkr93
GenerateQuery is not a OOTB function or component. In your case this is just a button. Please share Java script function which is getting called on click of it. There must be some error in that JS .
Thanks
Dipti
Hi, can you try to move rows="3" in granite:data node?
Views
Replies
Total Likes
Views
Replies
Total Likes
Hi @rajnishkr93
Compare the logic/markup of Resource (sling:resourceType of dialog fields) used for source element Button (Generate Query) and the target element (textarea) prior to and after Migration.
On a very high level, it could be the identifiers (class/id or HTML tag name) or if you are relying on custom properties on a dialog field node.
Share the complete dialog resources used and custom JS for debugging further.
Views
Likes
Replies