Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 5 of 5

Thread: Questions about custom Product attributes

  1. 02-18-2010, 10:01 AM #1
    lhanssen is offline Junior Member
    Join Date
    Feb 2010
    Posts
    2

    Default Questions about custom Product attributes

    I'm and experienced .NET developer just getting started with AspDotNetStorefront ML 8.0.1.2. I have looked through the database and have studied how the entities work from a conceptual standpoint while at the same time perusing the online manual and admin area.

    Our customer has products with many custom attributes (maybe 10-15). I've searched this forum and have seen suggestions for ways to handle this is: extension data and kits.
    After looking more closely at both, they are not acceptable to our client. I'm now looking at customizing the product.

    It appears that I'll need to following:
    1. add columns to the Product or ProductVariant table (which is more appropriate? I'm guessing ProductVariant)
    2. edit either admin/entityEditProducts.aspx OR admin/entityEditProductVariant.aspx depending on table modified
    a. looks like the sql is inline instead of stored procs
    b. add my own validation and handle my own tool tips
    3. edit any stored procs that grab data to display in the xmlpackages (I've seen examples on this forum) by adding the new columns
    4. edit any xmlpackages for display that need my new data

    Can someone confirm that I'm going the right direction?
    Are there going to be any obstacles I might encounter that I didn't think of?
    I'm trying to get a sense of the full scope of work so I can plan my time and keep in line with our budget.

    Thanks.
  2. 02-18-2010, 11:59 AM #2
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    Sounds like you've covered most of it. The only other thing I can think of offhand would be to adapt one or more of the import tools (Excel, XML, or WSI) to allow your client to bulk upload those new elements. Depending on the number of products they sell, manually setting up each product might take a while with an extra 15 attributes.
    ECommerce Shopping Cart
  3. 05-21-2010, 10:15 AM #3
    rocketTendon is offline Junior Member
    Join Date
    May 2010
    Posts
    2

    Unhappy Surprised

    I'm kind of surprised that custom-attributes based on product-type doesn't exist out of the box (or even just custom-attributes not based on product-type)... given all the thought that has been put into this product.

    With our products... we have several attributes that we need to be made available in "advanced search".

    Do you guys have plans to implement this in the future?

    Feature-suggestion I suppose.
  4. 09-28-2010, 07:15 AM #4
    McJoe is offline Member
    Join Date
    Oct 2007
    Posts
    50

    Default

    This is a frequent request by our customers. Aspdotnetstorefront should invest some time to implement this or get a 3rd party to make a good plug-in.
  5. 09-28-2010, 02:40 PM #5
    philipb is offline Junior Member
    Join Date
    Jul 2010
    Location
    Ft. Lauderdale, Florida
    Posts
    22

    Default

    We are also in this situation. The products we sell have a large number of custom attributes (size, material, color, component type, component shape, to name a few) in a variety of permutations, depending on product type.

    In addition to the changes outlined by lhanssen, the Orders_CustomCart table & corresponding code infrastructure may need to be modified as well, not to mention the product template being used & the invoicing, receipts, etc used for order processing.