XPages: Edit multi-value fields in existing documents - A frustrating battle!

It's been a while since I last wrote something on here, I'm blaming it on a very busy schedule, but now there's something I would very much like to share with the rest of the XPages Community: During the last couple of months, I've been (amongst other things) working on implementing an "edit news article"/"edit user profile" feature on website I'm creating. I've previously developed a "create news article". This XPage contains the usual "heading", "lead paragraph" and "body" fields, but also some multi-value fields to select category and target audience for the news article.

The creation of these multi-value fields were fairly straight-forward, and creating news articles worked like a dream. However, trying to edit these fields on an XPage was to be a more painful experience. Changing the values and hitting the save button on the site would not have the desired effects on the saved Notes document, the multi-value fields would remain unchanged. The whole thing was getting very frustrating, but fortunately there are some explaining and helpful articles out there on the web:

• Sean Cull has created a page that demonstrates the the differences between a field's value and submitted value. Take a look here.
• IBM have written something themselves about the topic, have a look here.
• YouAtNotes.de writing about getting and setting field values and value bindings here.

I hope these links will prove to be as helpful to some of you as they were to me!

XPages: Default Value for Repeat Limit in Repeater Control Equals 30 ?

Last week, I stumbled upon a mysterious bug in XPages. I've created quite a few pages and custom controllers with repeater controls during the last months, but never seen this before:

When I didn't specify a repeat limit for the control, I would only get the first 30 entries from the data source!

I've developed the habit of not setting the repeat limit when I don't need it, believeing that it would provide me with all the entries from the data source. Checking the provided documentation in the Domino Designer comfirmed my thoughts:

Has anyone else experienced this bug? Or is there another way to limit the repeat control, that I might have done unintentionally?

For most cases, the work around is quite easy, just set the repeat limit field to some high value that you (probably?) will never exceed, but in some cases you might not know in what range the number of view entries will be when your application has been in use for a while...