Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

Adative form core component Number Input Core Component's Display Pattern dropdown not appearing

Avatar

Level 6

Number Input Core Component's Display Pattern dropdown not appearing in the OOTB Adaptive Form template (blank-af-v2) but working when the same component is used in your own custom project (/conf/myForm/...) — even though the versions are the same .

 

Working as expected for myForm Project with  /conf/myForm/settings/wcm/templates/blank-af-v2 

varaande_0-1752756018284.png

MyCore component project even though both refereing core/fd/components/form/numberinput/v1/numberinput

varaande_1-1752756159689.png

 



 

1 Accepted Solution

Avatar

Correct answer by
Employee

@varaande This doesn't depend on core component version, it depends on content policy configured in template. If you use the latest archetype to build the project, it will be added to the template created under the appid for your project. We have also added these content policies to examples as well https://github.com/adobe/aem-core-forms-components/tree/master/examples/ui.content/src/main/content/...

In up coming August release it will be available in OOTB templates, if you are on cloud.

View solution in original post

3 Replies

Avatar

Moderator

@varaande we tried to reproduce the disabled error. It seems to be working for us. Can you share your console logs?

Avatar

Level 6

@Khushwant_Singh 

The Core Component Number Input field loads the default display pattern list only when a policy is defined at the Adaptive Form Core Component template level. Without this, it won’t display the pattern options automatically.

Additionally, to populate the language dropdown, instead of adding all 47 locales through the fd:supportedLocales multi-value property, it’s recommended to add each language as an individual property—for example:
lang1 = "English=en-US"
lang2 = "French=fr-FR"

Avatar

Correct answer by
Employee

@varaande This doesn't depend on core component version, it depends on content policy configured in template. If you use the latest archetype to build the project, it will be added to the template created under the appid for your project. We have also added these content policies to examples as well https://github.com/adobe/aem-core-forms-components/tree/master/examples/ui.content/src/main/content/...

In up coming August release it will be available in OOTB templates, if you are on cloud.