Highlighted

drop down is not retaining value in composite multifield

hpathan

22-02-2018

I am using granite/ui/components/coral/foundation/form/select inside coral multifield.

If I select any value in drop-down and submit the dialog, value is stored in jcr:content  but if I open the dialog again drop-down does not populate stored value.

I am working on AEM 6.3 SP1 Cumulative package 2, coral ui 3 and for multifield I am using acs-commons-3.14

Replies

Highlighted

smacdonald2008

22-02-2018

Just tested the package in this article and the Select field in the MF is holding the value when you close and re-open the dialog. See the SIZE field. As mentioned in this article - when using the Granite/MF type - you do not need to use ACS-Commons like you do when using the Granite Multifield.

MF11.png

Highlighted

smacdonald2008

22-02-2018

If you do not get the same results - lets setup a Connect Session. Try installing the package on a fresh AEM 6.3 instance to see this working.

Highlighted

hpathan

27-02-2018

It is working fine on my environment, but it is storing multi-field value is in node structure.  I want to store multi-field value in json format for that we are using acs-common.

Highlighted

hpathan

27-02-2018

I want to store multi-field value in json format. It working fine and storing but storing in node structure. Is there any way to achieve?

Highlighted

smacdonald2008

27-02-2018

why do you want to change how 6.3 granite/coral MF internally stores data. This is never seen by users. Its hidden.

Highlighted

hpathan

28-02-2018

We are migrating existing component from classic to touch UI, classic UI is storing data in JSON and it has been used in many production pages. Without breaking the system we need to setup touch UI dialog such like that it will store and retrieve existing JSON.

Highlighted

smacdonald2008

28-02-2018

There is no way to make that change. The coral/granite MF stores data as nodes.

you need to build your AEM 6.3 components using the functionality that the coral/granite resource types provide As opposed to making them work like classic ui components.