Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #30993 Back to Issue ]
Summary 0030993: It is not possible to define a preference as default value when column has a default defined in ad_column
Revision 2015-10-05 09:40 by alostale
Steps To Reproduce -Define a Preference with.
  * attribute='M_PRODUCT_CATEGORY_ID' (Note M_Product.M_Product_Category_ID has a default value in Table > Column)
  * value=ID_OF_ONE_EXISTING_CATEGORY (different that the first one on the dropdown)

-Select the visible at fields to apply to your client and the product window
-Logout and login
-Access to product window
-The product category fields has not got selected as default the category you defined. The default value is the first element of the dropdown.
Revision 2015-10-05 09:40 by alostale
Description Right now it is possible to default value by using a preference defined with attribute using the column name, and the default value you want on the value field.

That works properly whenever the column for that field has not a default value in AD, but it case it has preference is not taken into account.
Revision 2015-09-30 17:26 by alostale
Steps To Reproduce -Define a Preference witH.
attribute='M_PRODUCT_CATEGORY_ID'
value=ID_OF_ONE_EXISTING_CATEGORY (different that the first one on the dropdown)

-Select the visible at fields to apply to your client and the product window
-Logout and login
-Access to product window
-The product category fields has not got selected as default the category you defined. The default value is the first element of the dropdown.
Revision 2015-09-30 17:26 by alostale
Description Right now it is possible to default value by using a preference defined with attribute using the column name, and the default value you want on the value field.
That works properly for most of the fields, but does not work if the fields is defined with tabledir reference.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker