Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events

Issue with persisted value on radio selection


Level 3


I faced a strange issue with radio button in a component dialog. I have a field with xtype=selection and type=radio with two options 1) Dynamic(default value) 2) Curated.

When content managers edit the component to choose any of the above radio buttons, the value stored against the property is either Dynamic or Curated.

But in one of the dev servers(running on AEM 6.0 SP3), the value of the property is stored as an string array [true,false]. We are sure that the property has not been modified manually through CRXDE. 

I am unable to replicate the scenario even after multiple attempts. If anyone has idea on how this was possible, could you please let me know.

Any inputs on this are highly appreciated.

PFA for the node structure and properties of the radio field.

3 Replies


Level 4

How have you created the dialog. Here is a nice article that walks you though creating a classic UI component with radio buttons:





Adding some referenc articles/Post for your help:-

Link:- https://forums.adobe.com/thread/1217812


        1. Create widget node -> xtype : selection , type : radio , name , field Label e.t.c
        2. create subnode -> Options  : type cq:WidgetCollection
        3. Create nodes of type nt:unstrutured , properties text and value

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

Link:- http://stackoverflow.com/questions/27520377/how-to-create-a-radio-button-in-aem-6-touch-dialog

Link:- http://www.willdev4donuts.com/dialog-radio-buttons/#.V2jW3Pl97RY

I hope this would be of some help to you.

Thanks and Regards

Kautuk Sahni

Kautuk Sahni


Level 3

Hi Steve & Kautuk,

Thanks for the response.

The radio buttons in the dialog were created in similar way as mentioned in the above links and it was working as expected for last 2.5 years.

Recently it was observed(on one single random page) that the value stored against the property for radio button was not a string but string array [true,false]. I am unable to understand how that was possible. We are not yet using Touch UI interface for authoring content, so this issue occurred while authoring content in classic mode.