I'm not sure why I didn't close this already: the issue it describes is now understood, and deals with it. The remaining part (wondering whether records should be created with empty subrecords) is its own issue in . So there is nothing left to be done on this one.

Let's discuss this (if more need be said) over on . I think what you're saying makes sense.

That's not how redux-form operates, afaik. It assembles a record to POST from what is filled.

I know that some modules will refuse records with embedded empty records, but I've seen that only with repeatable sub-records - embedded arrays in other words - I thus found I had to amend such records with ui-okapi-console/utils/removeEmptyObjectsFromArray.js.

In this case, however, the embedded structure 'personal' does not repeat / is not an array, so mod-users might accept a record with an empty 'personal', I don't know.

I think I'd be for simply making the UI more tolerant of the back-end responding with records where non-mandatory elements are missing.

Haha, OK, knowing the cause, the pattern now makes sense.

Searching for "a" will break the display if username is the presently selected sort criterion, since then it will sort to the top. But if one of the other criteria is selected, then its undefined values make it sort to the bottom, and it never gets displayed – so the first ten records do display all right.

Similarly, sorting by username breaks the display if the currently selected set of records includes the bad one – because the username sort brings it to the top.

The problem here is (I think) that record creation should make all parts of the record, even if the fields are empty. At least, that's what I am going to file, and Niels-Erik can argue if he wishes

So that resolves the problem of why the weird state persists across browser reloads – good!

But it doesn't really explain why the manifestation of the bug is so erratic. Why does a search for "a" sometimes result in a list with the bad record that breaks the display? And why does it sometimes (apparently) omit that record, so that the ones it does return can be successfully displayed?