column values in list view (bug?)

[ststoddard]

A curious observation: when I go to list view or details view, the values for certain fields are not visible. If I go into the edit view, the values are there. These are fields that are filled in using the autocomplete feature.

This particular behavior is annoying, mostly because users make a fuss about the values being missing, when in reality they are not (I see them fine in the database).

Has no one else experienced this?

[shannah]

By "autocomplete" do you mean that these fields use a valuelist and a select widget? If so, is the valuelist defined in the valuelists.ini file or in the delegate class?

Can you give some specifics about the fields that are doing this (e.g. column types, fields.ini file definitions, relevant valuelist definitions...)

-Steve

[ststoddard]

So I use an autocomplete widget to pull a list specified in the valuelists.ini file as an __sql__ statement. Simple "SELECT distinct(names) FROM mytable." Table has about 4000 entries, several hundred distinct values.

I pull names and addresses. All varchar(x). In all cases I get a 'holy' response -- some records show, some don't.

If I go in to edit, the correct value shows in the field.

If I change the value to something other than what comes up automatically, then it sticks and shows in the details and list views.


You make a curious allusion -- how would one specify the values of a valuelist in the delegate_class? This would be useful to generate lists conditional on values entered in a related form...

[shannah]

This is strange. I'm not sure what would cause this behavior.

Do you notice any patterns on which ones show up? Common characteristics of the names that do show up, or don't show up?

There are some examples of defining valuelists in a delegate class in this thread: http://xataface.com/forum/viewtopic.php?t=3961#19797