Steps to reproduce

1. Configure a content type with a date field
2. Configure a default app uses that content type
3. Open configured app and create an item, choose a date value and save the item
4. Reopen saved item to see that the date field has not been retrieved nor populated
5. Edit some content, not the date field, then save it
6. Double check from JCR to see that the date field content has been wiped out to an empty value

Expected results

1. Date field should be populated and stored correctly
2. Do not loose customers' content

Actual results

• See above

Workaround

• use decoration to use jcrMultiField instead of jcrMultiValueField (on 6.3 one can use multiValueField)

  !content-type:breakOffer
  name: breakOffer-app
  label: Break Offer
  subApps:
    detail:
      form:
        properties:
          dates:
            $type: jcrMultiField 

Development notes

• Logs:

  2023-02-24 14:39:11,416 WARN  .apache.commons.beanutils.converters.DateConverter:     DateConverter does not support default String to 'Date' conversion.
  2023-02-24 14:39:11,417 WARN  .apache.commons.beanutils.converters.DateConverter:     (N.B. Re-configure Converter or use alternative implementation)
  

• Stackoverflow: https://stackoverflow.com/questions/5757242/java-beanutilsbean-convert-date-to-string
• This may happen due to updated in the library and the backward compatibility of the newer versions with its previous one.
• Example content type definition: breakOffer.yaml
• Example content app using content type: breakOffer-app.yaml