Difference between revisions of "Custom fields for user's profile"

From AbleCommerce Wiki
Jump to: navigation, search
m (New page: AbleCommerce 7.0 has the back end support that Merchant could store customer information for a user that only the merchant would update on the user's/customer's profile. .. ie.. an account...)
 
 
Line 1: Line 1:
AbleCommerce 7.0 has the back end support that Merchant could store customer information for a user that only the merchant would update on the user's/customer's profile. .. ie.. an account number, special note, cross-reference to another user, etc.
+
AbleCommerce 7.0 has the back end support that Merchant could store customer information for a user that only the merchant would update on the user's/customer's profile. i;e; an account number, special note, cross-reference to another user, etc.
  
There is a User.Settings property, which connects to a UserSettingsCollection class. The data here is persisted to the database and associated with the user. It would be the natural place for this kind of data.Some one who would like to have custom fields for the customers then he/she just have to build some admin UI to access and work with this field.
+
There is a '''User.Settings''' property, which connects to a '''UserSettingsCollection''' class. The data here is persisted to the database and associated with the user. It would be the natural place for this kind of data. If anyone wants to have custom fields for the users then he/she should make use of User.Settings. For any field that you want to be able to manage, you can add some UI to access and work with this field.
 +
 
 +
[[Category:AbleCommerce 7]]

Latest revision as of 11:16, 15 August 2013

AbleCommerce 7.0 has the back end support that Merchant could store customer information for a user that only the merchant would update on the user's/customer's profile. i;e; an account number, special note, cross-reference to another user, etc.

There is a User.Settings property, which connects to a UserSettingsCollection class. The data here is persisted to the database and associated with the user. It would be the natural place for this kind of data. If anyone wants to have custom fields for the users then he/she should make use of User.Settings. For any field that you want to be able to manage, you can add some UI to access and work with this field.