Relationship: User: Representative node bug?

I am using Views 3.3 and the latest dev version of the References module. I have a view of type user and am trying to also bring in the most recently created node of type 'employee' created by those users in that same view.

I recently discovered the 'Representative node' relationship. When I use that, it works ok but gets me the latest node created by that user of any node type, not just the one I need. So I am trying the advanced 'Representative view' feature. I couldn't find much documentation about it but all views that I try (even fairly simple ones with no filters) fail. Do I need something special in those views, like an argument? Right now the simplest I set up is a representative view with a Content: nid field and sorted by created descending. The SQL that gets generated in the main view using the representative view is:

SELECT users.picture AS users_picture, users.uid AS uid, users.name AS users_name, users.mail AS users_mail, node_users.title AS node_users_title, node_users.nid AS node_users_nid
FROM
{users} users
LEFT JOIN {node} node_users ON (SELECT nodeINNER.nid AS nidINNER
FROM
{node} nodeINNER
LEFT JOIN {users} users_nodeINNER ON nodeINNER.uid = users_nodeINNER.uid
WHERE (( (users_nodeINNER.uid = users.uid ) ))
ORDER BY node_createdINNER. DESC
LIMIT 1 OFFSET 0) = node_users.nid
INNER JOIN {users_roles} users_roles ON users.uid = users_roles.uid
WHERE (( (users.status <> '0') AND (users_roles.rid IN ('3', '4', '5', '6')) ))

MySQL throws an error at this line:
ORDER BY node_createdINNER. DESC

As you can see it tries to order by 'node_createdINNER.' rather than by the (I think correct) nodeINNER.created.

I am not sure if this is a bug or I am incorrectly configuring the representative view, but it smells like a bug to me. :)