User definable fields
-
Hi, Does anyone know where to find best practices on allowing users to create user definable fields. I have tried a few methods in ASP30. I am trying to figure out the proper way to do this. Salesforce.com has a feature inside the program where a user and create as many fields as they like. They have many fields to choose from. I don't fully understand how to pull this off in a RDMS. I have tried creating many "blank" fields of each type: varchar, datetime, text, bit. The system salesforce uses seems to not be bound by a certain number of colums. I assume they are actually altering each clients db schema. What ways have any of you guys allowed your users to create new fields on the fly? Where are some good articles on this subject? And also, what do you call this, I must not be searching using the correct words? Thanks, Jon Vickers
-
Hi, Does anyone know where to find best practices on allowing users to create user definable fields. I have tried a few methods in ASP30. I am trying to figure out the proper way to do this. Salesforce.com has a feature inside the program where a user and create as many fields as they like. They have many fields to choose from. I don't fully understand how to pull this off in a RDMS. I have tried creating many "blank" fields of each type: varchar, datetime, text, bit. The system salesforce uses seems to not be bound by a certain number of colums. I assume they are actually altering each clients db schema. What ways have any of you guys allowed your users to create new fields on the fly? Where are some good articles on this subject? And also, what do you call this, I must not be searching using the correct words? Thanks, Jon Vickers
I don't have any links to any Best Practices documents. However I've seen how it was done in Goldmine (sales contact manager). They use a table of custom field definitions where each row defines a custom field. The actual values are put in a separate table with ID fields to link to the FIELDDEFS table and the table the custom field is associated with. As far as storing different datatypes in .NET I would just make all of the actual data fields varchar and store the data using ToString(). Integer.Parse(), DateTime.Parse(), etc can be used when you retrieve the data. I hope this can get you started. I can give you a more detailed description tomorrow when I get to work and look up how exactly it's done. Laterness... Doug
-
I don't have any links to any Best Practices documents. However I've seen how it was done in Goldmine (sales contact manager). They use a table of custom field definitions where each row defines a custom field. The actual values are put in a separate table with ID fields to link to the FIELDDEFS table and the table the custom field is associated with. As far as storing different datatypes in .NET I would just make all of the actual data fields varchar and store the data using ToString(). Integer.Parse(), DateTime.Parse(), etc can be used when you retrieve the data. I hope this can get you started. I can give you a more detailed description tomorrow when I get to work and look up how exactly it's done. Laterness... Doug
Yea, Thanks, any articles or help would be appreciated. I have pulled this off a few different ways. I have a feeling there must be a better way. I feel like I am reinventing the wheel. Thanks, Jon Vickers