Oct 7th, 2009, 11:40 AM
Hey FutureMedia,
Thanks for your post! The explicit example and use-case really helped me make sense of it. This is clearly an issue that presents an real problem for some users, so sure, I'll add this feature.
What I'm going to do is this:
- Add a new section (optional, and hidden by default) called "Dynamic Client Filters" (or something less verbose...) at the bottom of the Edit View -> Filters tab. This section will look and function in a very similar way to the existing filters table where you can add your filters. Except in this new section, the final column will contain a dropdown of all client account fields. This will also contain any extended client fields, added via the Extended Client Fields module. You can then map the form fields to the client fields.
I'm hoping that this will also help mitigate the extra work involved in the use-case you mentioned. It should allow you to create far less Views - only one, in fact - so editing the Views to add / remove a field is considerably less work.
My one concern at this point is that Views that use these new "dynamic client filters" won't be able to be used outside of Form Tools, e.g. via the API in your webpages. These Views will now require a logged in user. Not sure how to handle that... anyway, something more for me to consider.
However, I MUST finish up this "Hooks Manager" module I'm working on first. I promised it to a user many months ago.
- Ben
Thanks for your post! The explicit example and use-case really helped me make sense of it. This is clearly an issue that presents an real problem for some users, so sure, I'll add this feature.
What I'm going to do is this:
- Add a new section (optional, and hidden by default) called "Dynamic Client Filters" (or something less verbose...) at the bottom of the Edit View -> Filters tab. This section will look and function in a very similar way to the existing filters table where you can add your filters. Except in this new section, the final column will contain a dropdown of all client account fields. This will also contain any extended client fields, added via the Extended Client Fields module. You can then map the form fields to the client fields.
I'm hoping that this will also help mitigate the extra work involved in the use-case you mentioned. It should allow you to create far less Views - only one, in fact - so editing the Views to add / remove a field is considerably less work.
My one concern at this point is that Views that use these new "dynamic client filters" won't be able to be used outside of Form Tools, e.g. via the API in your webpages. These Views will now require a logged in user. Not sure how to handle that... anyway, something more for me to consider.
However, I MUST finish up this "Hooks Manager" module I'm working on first. I promised it to a user many months ago.
- Ben