SUGGESTION: Type property for specification attributes

Now all specification attribute values are displayed as plain text. It would be very useful to have a "type" property that would define the way the value will be displayed in the product detail: text (default), link, PDF download, Excell download or HTML text. Thus it will give a lot of flexibility for attaching user manuals, brochures, (http://www.tiendacanon.com.mx/REBEL-T3-BK-EF-S-18-55-DCIII-Negro#.Ux9K8D9dWSo]example in "folleto" tab) , specification tables, Excel sheets, etc. or making links or displaying specifications with more flexibility.

Hi Eduardo,

Thanks for suggestion. Please vote here

Other suggested types: color square, image

Another suggestion would be: Product Squares

If the type is Product Squares, then the attribute values would display a series of Product Squares (Product Images inside the squares) for the customer to choose from. The admin would choose the products to display in the squares

Done. Please see changeset c370d430481a.

Please also vote for work items 12301 and 12302 and 12303 (support for other attribute types).

Could we get int/double values? Bonus points for being able to filter with a 'between' condition. i.e. Height between 10" and 15"

Boolean would be good, too. Otherwise we have to just go add "Yes/No" options to each Boolean type attribute.

So basically, a good chunk of CLR primitive types ;) bool, double, float, decimal (format as money). I think all of these would be useful. At least for me :)

Thanks a lot for suggestions. Please vote for this work item here

breakskater wrote:
We have attribute types (option, text, etc) applied to a mapping between specification option and a product. But we need it to be applied to "SpecificationAttribute" entity in order to support this new functionality. It's possible. But what should we do with the existing functionality when attribute type is specified when mapping an attribute option to a product (on a product details page > specification attributes tab). How should we migrate specified types to "SpecificationAttribute" entity? Especially considering that a store owner could specify distinct types for distinct products.

still thinking about better way to manage it

I don't really get the "product square" -- but it sounds like this could also be a good opportunity to refactor the issue where you have to have an option added even if you're just using custom text or whatever ;)