Multi select dropdown metadata schema field corrupting data

[subsul1]

Env: AEM as cloud service 6.5

I've got a custom metadata schema applied for certain asset folders.

Its got a multi select drop down field.

I'm noticing this weird behaviour where multi select field is not behaving as expected.

Steps to reproduce:

1. Open asset properties and choose multiple options for the drop down field and click save. Say you've selected 3 options.
2. Field gets saved as string array in jcr
3. Open the asset properties again, don't make any changes, just save it.
4. Notice the first element in the array gets deleted and is replaced with an empty entry. Network call indicates a call to @delete.
5. This happens until the array is completely emptied

Screen recording of the issue:

https://www.awesomescreenshot.com/video/5214107?key=e58794cc1f0dd94a89686f42287a7c99

Network console form data:

./jcr:content/metadata/dc:language:

./jcr:content/metadata/dc:language: ar_ye

./jcr:content/metadata/dc:language: be_by

./jcr:content/metadata/dc:language@Delete:

I believe the last entry is causing the issue.

I tried adding below to the field schema

deleteHint={boolean}true

deleteHint={boolean}false

Still deletes entries during save and close.

[diksha_mishra · Accepted solution]

@subsul1  you have explained the issue very well. As per my experience, this seems more like a bug with the AEM 6.5 cloud instance. It would be best to open a daycare ticket with Adobe Support. The team should try reproducing the issue and provide a fix accordingly. 

[subsul1]

Thanks for the update Diksha, I'll create a ticket.

[manpreetk908]

Hi,

Can you verify this behavior in any out of the box multi select dropdown? This will help you to isolate if it is a product or a custom field issue. In case of product issue, a daycare ticket might help.

Regards,

Manpreet

[subsul1]

Yep, can confirm this is happening to OOTB fields as well. Will create a day care ticket.

[kchaurasiya]

@subsul1 Even i faced this issue in past. As you have already raised a ticket with Adobe. You can post it here once it is resolved.

Thank You.