Hi deepakt84913413​The code I have shared has a comparing code already working on mobile sites, also you can use the below piece of code on initialize of root panel or the field to achieve what you want (validation to trigger when you leave the field.$(".numericbox1518941620523 input").focusout(func...

deepakt1812​Yes, James R Green​ is right.Why don't you use HTML5 number field in your forms. I have created a blog post here with a step by step way to achieve what you want.Numeric Box Widget Tips in Adaptive Forms for Mobile Devices | AEM Forms Blog It works in mobile also, with all the rules. Ple...

deepakt84913413​ :Why don't you use HTML5 number field in your forms. I have created a blog post here with a step by step way to achieve what you want.Numeric Box Widget Tips in Adaptive Forms for Mobile Devices | AEM Forms Blog It works in mobile also, with all the rules. Please go through the blog...

Hi Malarvizhi Saravanan​ :I would suggest you to use AEM's Content Services to achieve what you want.I is the best solution to your problem, giving you granular control over the data you would like to expose via the API.Cheers,JagjeetAEM Forms Blog

I am from Adobe (not from Forms' Engineering Team), so not an official word. But as far as I know changing the Form Model will lead to binding errors on all the bound fields, this may be an important reason to not allow it in first place.Cheers,Jagjeet SinghAEM Forms Blog

chandran85965395​  you need to add display:none to the selector ".guideFieldDescription.long" which is the parent to the cross button.You can do this by creating a client lib, creating a js file this code and add it as a dependency in your Adaptive form.Hope this helps !!!Cheers,Jagjeet SinghAEM For...

Hi James R Green​, formatix​,First of all that's definitely not a recommended way.If you still wish to go ahead and change it, please change it in the corresponding form location in /content/forms/af/***//jcr:content/guideContainer node also.Cheers,JagjeetAEM Forms Blog

I don't think this is a bug.There is a point we are missing here, since that field is mapped to an XFA element, it is supposed to have values that only XFA dropdown is mapped to.The right approach to handle your scenario should be to have the dropdown dynamic in XFA itself. The process remain almost...

So, I guess final correct answer should be add below mentioned code to code editor on initialize:guideBridge.on("bridgeInitializeComplete", function (event, data) {   guideBridge.resolveNode("staticText1").value = "Your new static text here";});I have created a blog post which delves into details ar...

As far as I remember, underscore's mapping was never present at that path, not even in 6.2.This seems like and issue, where you added some custom underscore client lib code at the wrong path, and that has been overwritten  when you upgraded your server.Cheers,JagjeetAEM Forms Blog