Because we use multiple column to define primary key. When use data entity, we assign entity id to serial integer field with index (not primary key), it worked.
But when using entityreference to get ajax popup list, views result will use primary key to it's index. It should respect what we set in data entity interface.
When looked into code, we found that entity force primary key(and only first one) to be views base table, we have small patch for this to respect what we set in data entity.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | data-views_base_id_repect_data_entity-2673132-4.patch | 546 bytes | jimyhuang |
Comments
Comment #2
jimyhuang commentedThis is our patch. To see if we can pass the test.
Comment #3
joachim commentedLooks like a reasonable change, but this should be in data_entity_views_data_alter(), so in Data Entity and not in Data module.
Comment #4
jimyhuang commentedMove change to data_entity_views_data_alter. Patch here.
Comment #5
roderikThis should also fix the 'edit item' link in the view, in such situations.
I don't have the setup to test this right now (just stopping by to crosslink a few issues), but it seems to me like people using the 'edit' link will be confused with the unpatched module, if their (single or multi-field) primary key happens to be different from the entity ID.