[IMP] stock: remove 'full' from context for locations, no longer useful

bzr revid: rco@openerp.com-20120113151647-mo7rprxwhqy589ki
This commit is contained in:
Raphael Collet 2012-01-13 16:16:47 +01:00
parent aa84c454ad
commit 6068fc44fd
2 changed files with 7 additions and 8 deletions

View File

@ -141,7 +141,7 @@
<field name="view_type">form</field>
<field name="view_mode">tree,graph</field>
<field name="search_view_id" ref="view_stock_search"/>
<field name="context">{'full':'1','contact_display': 'partner','search_default_done':1,'search_default_year':1, 'search_default_month':1, 'search_default_group_type':1, 'group_by': [], 'group_by_no_leaf':1,}</field>
<field name="context">{'contact_display': 'partner','search_default_done':1,'search_default_year':1, 'search_default_month':1, 'search_default_group_type':1, 'group_by': [], 'group_by_no_leaf':1,}</field>
<field name="help">Moves Analysis allows you to easily check and analyse your company stock moves. Use this report when you want to analyse the different routes taken by your products and inventory management performance.</field>
</record>
<menuitem action="action_stock_move_report" id="menu_action_stock_move_report" parent="next_id_61" sequence="3"/>

View File

@ -186,7 +186,6 @@
<field name="res_model">stock.inventory</field>
<field name="view_type">form</field>
<field name="view_id" ref="view_inventory_tree"/>
<field name="context">{'full':'1'}</field>
<field name="search_view_id" ref="view_inventory_filter" />
<field name="help">Periodical Inventories are used to count the number of products available per location. You can use it once a year when you do the general inventory or whenever you need it, to correct the current stock level of a product.</field>
</record>
@ -407,7 +406,7 @@
<field name="view_type">form</field>
<field name="view_id" ref="view_production_lot_tree"/>
<field name="search_view_id" ref="search_product_lot_filter" />
<field name="context">{'full':'1',"search_default_available":1}</field>
<field name="context">{"search_default_available":1}</field>
<field name="help">This is the list of all the production lots (serial numbers) you recorded. When you select a lot, you can get the upstream or downstream traceability of the products contained in lot. By default, the list is filtred on the serial numbers that are available in your warehouse but you can uncheck the 'Available' button to get all the lots you produced, received or delivered to customers.</field>
</record>
<menuitem action="action_production_lot_form" id="menu_action_production_lot_form"
@ -584,7 +583,7 @@
<field name="view_type">form</field>
<field name="view_id" ref="view_location_tree2"/>
<field name="search_view_id" ref="view_location_search"/>
<field name="context">{'full':1, 'search_default_in_location':1}</field>
<field name="context">{'search_default_in_location':1}</field>
<field name="help">Define your locations to reflect your warehouse structure and organization. OpenERP is able to manage physical locations (warehouses, shelves, bin, etc), partner locations (customers, suppliers) and virtual locations which are the counterpart of the stock operations like the manufacturing orders consumptions, inventories, etc. Every stock operation in OpenERP moves the products from one location to another one. For instance, if you receive products from a supplier, OpenERP will move products from the Supplier location to the Stock location. Each report can be performed on physical, partner or virtual locations.</field>
</record>
<menuitem action="action_location_form" id="menu_action_location_form" parent="menu_warehouse_config"/>
@ -1420,8 +1419,8 @@
icon="gtk-convert" context="{'scrap': True}"
states="draft,waiting,confirmed,assigned" colspan="1"/>
<newline/>
<field name="location_id" context="{'full':True}"/>
<field name="location_dest_id" context="{'full':True}"/>
<field name="location_id"/>
<field name="location_dest_id"/>
<field name="address_id" context="{'contact_display':'partner'}"/>
</group>
@ -1608,8 +1607,8 @@
icon="gtk-convert" context="{'scrap': True}"
states="draft,waiting,confirmed,assigned" colspan="1"/>
<newline/>
<field name="location_id" context="{'full':True}"/>
<field name="location_dest_id" context="{'full':True}"/>
<field name="location_id"/>
<field name="location_dest_id"/>
<field name="address_id" context="{'contact_display':'partner'}"/>
</group>