I hope that someone will tell me that I’m simply missing something very obvious …
I’ve just updated to 7.0.3. In a view the rows height is set to 3 lines. A column in this view contains a multi-value field. The multi-value seperator of the view is “New Line”. Very simple!
In 7.0.2 a multi-value field was displayed in that view on multiple lines. In 7.0.3 the elements of the field stick together on the same line. I simply cannot believe that this is an error in 7.0.3 and keep on hoping that I missed something simple.
Thanks very much for any help
Ruedi
Subject: Multi-Value seperator “New Line” in view not working in 7.0.3?
Works for me. No problems here, Server and Client running on 7.0.3.
Subject: RE: Multi-Value seperator “New Line” in view not working in 7.0.3?
Thank you. I just found out that the problem only occurs when the multi-value data contains an umlaut (ä,ö,ü) or some other non-ASCII character (like é,à etc.). Would you mind checking whether that works for you?Ruedi
Subject: Multi-Value seperator “New Line” in view not working in 7.0.3 => BUG
Huh, you’re right.
Now I see the same behavior. Unfortunately, I don’t even see a workaround for this. @Implode(FieldName; @NewLine) does not work in a column formula.
Subject: RE: Multi-Value seperator “New Line” in view not working in 7.0.3 => BUG
Great! Well, not really, but many thanks for reproducing the problem.
In the meantime I’ve found further informations confirming the problem (and even giving a solution).
Article in english describing the problem and presenting a solution:
http://www.eknori.de/2008-01-11/notes-703-problem-with-german-umlauts/
Discussion in german about the problem:
Additional information and warnings from IBM:
http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21227261
http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21233550
Subject: RE: Multi-Value seperator “New Line” in view not working in 7.0.3 => BUG
Ha, that’s a clear indication of getting old, I suppose:
I had actually read Eknori’s posting, but completely forgot about it in the mean time. The only good thing about it is, that this is “just” a client issue …