[ 
https://issues.apache.org/jira/browse/OFBIZ-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802341#action_12802341
 ] 

Scott Gray commented on OFBIZ-3307:
-----------------------------------

Hi Hans,

As I mentioned in my previous comment, I don't believe that ProductTypeAttr was 
intended as being the only way to manage ProductAttribute records, if it were 
then foreign keys would enforce the relationship and not allow for arbitrary 
attrNames.

I'm not sure what you mean by maintaining SalesChannel and ProductTypeAttr 
records in webtools, do you mean that the user should just manually enter the 
records using the entity data maintenance tools?  If so I don't think that is 
an ideal solution for either entity.

IMO the best solution would be to add a screen to the catalog app for 
maintaining ProductTypeAttr records and then also add another form to the 
Product -> Attributes screen so that the user has a choice of either creating a 
record based on a predefined ProductTypeAttr or to create a new arbitrary 
ProductAttribute record.

I have no desire to implement these features and was merely trying to resolve 
some bugs in my spare time.  My preference would be revert the current change 
simply because it removed functionality that was previously available to users. 
 It has obviously had a negative effect or otherwise this issue would never 
have been created.

> Error in product attributes page.
> ---------------------------------
>
>                 Key: OFBIZ-3307
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3307
>             Project: OFBiz
>          Issue Type: Bug
>    Affects Versions: SVN trunk
>         Environment: Linux Fedora Core 9, Postgres.
>            Reporter: Rohit Sureka
>            Assignee: Scott Gray
>             Fix For: SVN trunk
>
>
> The 'Add Product Attribute' has a drop down list for attribute name. if the 
> product does not already have a existing product, its not possible to add a 
> new attribute, since the attribute field is a required field but which is 
> blank. This problem does not exist in R9.04 where it was not a dropdown but a 
> simple text field .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to