openerp-india team mailing list archive

[Grégoire Krieg (OpenERP) <1122229@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Tested on local environment, on revision of server 4831

Head to Settings > Technical > User Interface > Views 
Create a new view and you will immediatly see invisibility of View Type. Then say you want to create the following view:

- View Name:  product.product.inherit2
- Object: product.product
- Sequence: 8
- Inherited View:  product.normal.form
- Architecture: 
<?xml version='1.0'?>
	 <field name='list_price' position='after'> 
	<field name="x_internal_number"/>
</field>

The idea here is to add custom field (x_internal_number) after the price
of product.

The workaround is to duplicate an exisiting view that inherits from
product.product and it works. But this workaround is case related and
what if someone would like to do it for an inherited view that doesn't
exist. Note also that the example case above was simple but what about
doing more complex xml code via the interface (not possible via view
editor).

 In any case this View Type should be selectable to avoid workarounds.

** Affects: openobject-server
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/1122229

Title:
  [7.0][ir.ui.view] Creating a view - invisibility of View Type field -
  Impossible to save

Status in OpenERP Server:
  New

Bug description:
  Tested on local environment, on revision of server 4831

  Head to Settings > Technical > User Interface > Views 
  Create a new view and you will immediatly see invisibility of View Type. Then say you want to create the following view:

  - View Name:  product.product.inherit2
  - Object: product.product
  - Sequence: 8
  - Inherited View:  product.normal.form
  - Architecture: 
  <?xml version='1.0'?>
  	 <field name='list_price' position='after'> 
  	<field name="x_internal_number"/>
  </field>

  The idea here is to add custom field (x_internal_number) after the
  price of product.

  The workaround is to duplicate an exisiting view that inherits from
  product.product and it works. But this workaround is case related and
  what if someone would like to do it for an inherited view that doesn't
  exist. Note also that the example case above was simple but what about
  doing more complex xml code via the interface (not possible via view
  editor).

   In any case this View Type should be selectable to avoid workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/1122229/+subscriptions