Jun 27th, 2009, 10:52 AM
Hi Diego,
Thanks for your post - and sorry I didn't respond earlier. I read over your post a couple of times but never got round to responding. Sorry!
Let me just make sure I understand what you need. I've received a number of similar requests to expand the way you can assign Views to clients, to prevent you from having to manually create Views for each client. It sounds like that's what you need, but just so I'm totally clear let me go over it.
So you have about 200 clients, each of which need to view a specific subset of the form data. Is this subset a particular set of submissions, form fields or both?
In terms of the UI, how would you like it to work? So when you create a new client, how would you map that client to your data subset? e.g. would there be a new field in the Add Client page that said "use View X", or would there be something in the View itself (where?) that would dynamically assign itself to the client based on ID, name or something else.
Please let me know your thoughts on this - be as specific as possible, too!
Also - just so you know what I've been thinking about. There's an existing "Extended Client Fields" module that lets you define whatever additional client fields you want. Maybe we could use that in conjunction with Views to help?
I'm just thinking in terms of how it should work from the user-interface perspective. My job is to make it as simple but as powerful/flexible as possible.
Thanks!
- Ben
Thanks for your post - and sorry I didn't respond earlier. I read over your post a couple of times but never got round to responding. Sorry!
Let me just make sure I understand what you need. I've received a number of similar requests to expand the way you can assign Views to clients, to prevent you from having to manually create Views for each client. It sounds like that's what you need, but just so I'm totally clear let me go over it.
So you have about 200 clients, each of which need to view a specific subset of the form data. Is this subset a particular set of submissions, form fields or both?
In terms of the UI, how would you like it to work? So when you create a new client, how would you map that client to your data subset? e.g. would there be a new field in the Add Client page that said "use View X", or would there be something in the View itself (where?) that would dynamically assign itself to the client based on ID, name or something else.
Please let me know your thoughts on this - be as specific as possible, too!
Also - just so you know what I've been thinking about. There's an existing "Extended Client Fields" module that lets you define whatever additional client fields you want. Maybe we could use that in conjunction with Views to help?
I'm just thinking in terms of how it should work from the user-interface perspective. My job is to make it as simple but as powerful/flexible as possible.
Thanks!
- Ben