Level 3

Aem 6.4 coral UI 3 touchui dialog default values not working

Forum|Forum|6 years ago
April 23, 2019
5 replies
13536 views

Hi,

My touchui value property is not working for textfields.

In the same way selected property is not working for the touchui select field.

I am using arm 6.4 and coralui3.

When I debug the code , when ever the cmp.getvalue().Val() is returning null and cmp.getvalue().isselected() methods is always returning false.

So if any cmp.getvalue().somemethod() the functionality is not working.

I have overridden the global.jsp and it is missing the componenthelper import.

The issue is intermittent.

Does the dialog structure causes the issues?

Where can I validate the dialog in aem?

How can I resolve the issue??

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

U

user05162

Adobe Employee

Have you tried installing SP3? There was a known issue with default values on 6.4.2

S

sr508Author

Level 3

Hi jaideep,

My instance doesn't have any SP installed.

It is 6.4.0.

Will install SP3 and try.

Is there any way to validate my dialog structure as well??

Ravi_Pampana

Community Advisor

Hi,

If possible try using cq:template node for default values

AEM Developer Learning : cq:template and cq:templatePath Properties of a Component in AEM

S

sr508Author

Level 3

Hi Ravi,

Tried with cq:template , it is working fine but some components still have the issue.

Does cq:template won't work if the dialog creation is not proper say structure or dialog tree etc.

Ravi_Pampana

Community Advisor

Hi,

Is it possible to share your _cq_dialog.xml to verify if anything wrong with the dialog creation.

smacdonald2008

Level 10

Have you going through this document. I have never seen any issues - esp with Select fields.

Building Experience Manager Components using Granite/Coral Resource Types

S

sr508Author

Level 3

Mine is not a HTL component.

It's a jsp with custom global.jsp .

Would that make any difference??

smacdonald2008

Level 10

Using JSP as opposed to HTL will not make any diff to the component dialog.

I strongly recommend that you go through the doc I posted. You will learn more about the GRANITE/CORAL resource types and more about HOW TO work with HTL - which reflects best practices.

Ravi_Pampana

Community Advisor

I dont think using custom global.jsp and using jsp instead of htl will have any effect on default value for dialog or using cq:template. Please check your _cq_dialog.xml structure is correct as per the link shared by smacdonald2008 above.