Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

After migration into CoralUI Query is not generating

Avatar

Level 3

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"/>

rajnishkr93_0-1626150483298.png

Please help me out !! Thanks in advance

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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. 

View solution in original post

5 Replies

Avatar

Community Advisor

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

Avatar

Community Advisor

Hi, can you try to move rows="3" in granite:data node?

Avatar

Level 3
Hi Arun, that approach dint work....it seems js is breaking somewhere

Avatar

Community Advisor
Can you share your javascript? The issue could be with data attributes or class which changed due to resource type.

Avatar

Correct answer by
Community Advisor

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.