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

Mandatory field is still red even though the field has value

Avatar

Level 3

Hi all,

I am using aem 6.4 in my touch ui component having one multifield tab inside that having one path field i marked as mandatory by using the property required Boolean true in this mandatory field is still red even though the field has value.

Expected is once the value is selected means that time that mandatory field highlighting red color should be disappear. 

Give me some solution to resolve this issue.

I attached some screenshot of my component below

Screenshot (523).png

Screenshot (524).png

Screenshot (525).png

   

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Basic Steps to Debug an Error in AEM, see what kind of useful logs you are getting, and share it with us. The required Granite UI 1.0 property-configuration comes out of the BOX from aem, which means that this problem shouldn't really exist. 

You should not add custom code to solve this problem, but see what the actual problem is, and possibly fix the problem by restarting your AEM, or upgrade your local AEM service-pack to the latest version. 

 

By the way, your configuration to the Touch UI field looks alright, but allowBlank is not really a configuration for the path field. Take a look at all the available configurations you can utilise with the official Granite UI 1.0 documentation > PathField — Granite UI 1.0 documentation (adobe.com)

 

I know it can be challenging to decipher the documentation to XML configuration, take a look a this blog article to learn with ease -> How to Convert Adobe’s Granite UI 1.0 Documentation to XML - Sourced Code

View solution in original post

6 Replies

Avatar

Level 5

You have to write a custom validator using foundation validation. Here I give you a glimpse of the code and steps to solve this problem for your reference.

Step1: Write custom JS to Register required fields in each multifield.

(function ($, window, document)
{
var registry = $(window).adaptTo("foundation-registry");
})
($, window, document);

Step2: Validate required fields.

(function ($, window, document)
{
var registry = $(window).adaptTo("foundation-registry");
registry.register("foundation.validation.validator",{
selector: "[data-validation=url-validate]",
validate: function (el)
{
var element = $(el);
var elementVal = element.val();
if(elementVal.length == 0)
{

return "Please enter URL";
}
else
{
return;
}

}
});
})
($, window, document);
Hope this Helps,

Aditya.Ch

Avatar

Community Advisor

Hi @Nandheswara ,

 

"allowBlank" is not pathfield property, please remove it and just keep the "required" property and check.
if it doesn't work, please copy a pathfield from core components, to avoid wasting time in debugging this.

Regards,

Sravan

Avatar

Community Advisor

@Nandheswara can you try this in incognito, maybe there is a conflict with your Browser's extensions?

Avatar

Community Advisor

Have you tried moving focus in the other input field or submitting dialog?

Can you also check if there are any console error when you empty the field and filled again?

Avatar

Level 3

Yes I tried to move the focus on others fields also still red highlight showing but when i enter some values in other fields means that highlight will gone and even in console also no errors

Avatar

Correct answer by
Community Advisor

Basic Steps to Debug an Error in AEM, see what kind of useful logs you are getting, and share it with us. The required Granite UI 1.0 property-configuration comes out of the BOX from aem, which means that this problem shouldn't really exist. 

You should not add custom code to solve this problem, but see what the actual problem is, and possibly fix the problem by restarting your AEM, or upgrade your local AEM service-pack to the latest version. 

 

By the way, your configuration to the Touch UI field looks alright, but allowBlank is not really a configuration for the path field. Take a look at all the available configurations you can utilise with the official Granite UI 1.0 documentation > PathField — Granite UI 1.0 documentation (adobe.com)

 

I know it can be challenging to decipher the documentation to XML configuration, take a look a this blog article to learn with ease -> How to Convert Adobe’s Granite UI 1.0 Documentation to XML - Sourced Code