are these functions added as mentioned in project page?
Filtering by any column of the entity table (instead of just the label).
Filtering by the value of any field of the entity.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

slv_’s picture

Not yet. This is planned because I see it a useful an probably common feature to have, but is not available yet because I didn't need it on the initial field type. I'll try to add it as soon as I find some time for it.

However, I'm happy to accept patches on that if you are willing to commit something!

kaizerking’s picture

Oh ok,
I am not coder so cant really code sorry about that
I am driven to this page to see if this would help me create a shopping cart where we can select product dynamic filtering by different fields kind of like a table with ajax submit cells as dependent fields inclduing Id, lable and unit of measure etc. of the products

slv_’s picture

Well, once the fields and column filtering are in place, this module might certainly be of help, but won't give you any of that as a drop-in solution. It's a helper for developers, and is not difficult to integrate with views exposed filters, so if there is any developer in your team, they should be able to use this as a helper module.

Hope that helps!

kaizerking’s picture

FileSize
11.57 KB
39.09 KB

Thanks for clarifying and it seems promising, I am just an enthusiast playing with Drupal so there is no team, no business.just interest.
Here I am attaching some libraries which may help you not that you require but may hep, I am not sure.
you can also see them in action at the following links

http://grider.sourceforge.net/index.php
http://boriscy.github.io/grider/

slv_’s picture

I don't think those libraries will help, but thanks for that! Just to clarify, when I say "entity table", it's nothing to do with an HTML.

The entity table is related to the storage of the different entities on the database, (so, for users, the 'user' table, for nodes, the 'node' table, and any custom tables for any other custom entities).

All entities in Drupal are supposed to have a label, which is the common name to identify them. For example, in nodes, this is the title, and in users, it is the username.

Right now, the autocomplete fields one can create with this module, query the database based on the label of the entity type you're looking for. By adding column and field filtering to the mix, it means that one could easily build an autocomplete field to search users, but instead of doing it by name, doing it by email, or address, or whatever info is stored on the database about users. That's what I was talking about, it's all related about how this module interacts with the database.

Thanks for your comments!

slv_’s picture

Status: Active » Closed (works as designed)

Closing. The filtering will be added, but this issue is based on a misunderstanding of terms. so better leave closed not to confuse people about what will be implemented in a next version of the module.

spacetaxi’s picture

Issue summary: View changes
Status: Closed (works as designed) » Needs review
FileSize
9.26 KB

A patch to allow for searching by field. Additional query settings for field(s) to search as well as option and key returned. Made accommodation for default field and search by property, but have not tested. Needed this functionality myself, happy to revise if requested.

spacetaxi’s picture

This is a revision of my first patch, and only adds a 'search' setting to the '#era_query_settings' array. This array will allow searching by multiple fields. If used, the 'search' fields take the place of the entity label for both option and key values shown.

spacetaxi’s picture

FileSize
10.87 KB

revision

spacetaxi’s picture

FileSize
12.05 KB

Probably was too quick to submit this. Here is the last patch for the time being.