"...displaying that is the human-understandable form of that particular object"
Ideally, yes. But when dealing with end users, things need to be simple and pretty. Output from permission object: <WPermission 17 permissionId=u'custom_query' description=None> The permission name is custom_query, but it's not easy to see and end users are likely to be confused. "Randall, what is this garbage on the screen?" I may be the only person that has this view or maybe fastdata interfaces aren't intended for Joe User. Here is one possible solution that won't break things. When passing in form_fields to DataController, a form_fields list item can be a tuple like list_fields arguments. The additional field is the name of the attribute to call on the data object to return a display name. If it was a dict instead of a tuple, this functionality could be further extended.
