#250 ✓resolved
Nathan B

'dynamic fields' for any model.

Reported by Nathan B | September 21st, 2011 @ 09:49 AM

Summary (what & why)

Allow models such as Contact, Account, Lead, etc. to have dynamic fields added via an admin interface.
These would include validations and field types. Future plans would include filtering and searching.

What are the details?

For example, instead of writing database migrations and hacking view templates to add a new field, any administrator could do this quickly via the admin interface.

We have written a 'supertags' plugin that could do with some refactoring, and a lot of that code could possibly be moved into core fat free crm. Our supertags plugin contains the concept of 'custom fields', and while the database backend needs to re-written, a lot of the front-end code could be re-usable.

We would use a table called 'dynamic_fields' to store custom fields for classes, and a polymorphic 'DynamicFieldValue' model to store values for those fields. 'parent_type' could be a standard model (Contact, Account, etc.) or even a special class such as Tag, which would replace the supertag functionality.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Ruby on Rails CRM platform for Web 2.0 and beyond

People watching this ticket