Workaround for Multi-Value Fields – Update

Home » Workaround for Multi-Value Fields – Update

Earlier this month I posted an article about multi-value field problems. The good news is it’s been SPR’d  – reference EGLN7YMLYD.

However, while looking into a fellow developer’s problems on this area, my mind wandered back to the XPages templates that have been developed by IBM, specifically the Discussion Template. Surely Tags (WebCategories field) is a multi-value field, does that have the same problem?

Answer, no.

The obvious next question – why?

After dissecting the differences between the two, reducing it to the most basic elements to reproduce the working functionality, and then add in the differences until it broke, I quickly identified the reason. The multi-value separator type. If it’s a comma, it works fine. If it’s a semi-colon, it breaks.

The comma works fine both for xp:inputText and xp:inputTextarea.

If only we could find a way to ensure users can ONLY enter a comma to separate values!

 

3 thoughts on “Workaround for Multi-Value Fields – Update”

  1. Comma works for xp:InputText when you save strings. It doesn’t work for number and date values. Tested in the demoapp I posted to be certain.

    Hopefully they will fix this along with the bug with “custom” separator.

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to Top