#odoo9

Odoo Fiscal Position 

Using Odoo SaaS is extremely limiting and most of the solutions to most of the issues you find online are programmatic solutions for when you have access to the models themselves. These, however, do not help you if you’re stuck on the SaaS platform. 

So many times I have wanted to display related data in one view from another model. Thanks to some help from a StackOverflow user, I understand how to do it now.. here’s the beta. 

In the model res.partner I created 2 new fields of type ‘Selection’ named ‘x_invoice_preference’ and ‘x_payment_preference’. I needed to display these preferences inside of the account.invoice tree and form views, and I definitely didn’t want the values to be copied, but referenced. 

I will explain the ‘x_payment_preferences’ solution in this example, but just rinse and repeat for your fields. The solution is to create a new field in account.invoice with the same name as the field in res.partner (this is not required, but is best practice). Give it a Field Label and click on the “Advanced Properties” tab.  Then put 

partner_id.x_payment_preference 

as the value for ‘Related Field’. This will automatically set the field type, same as the related field. You then need to copy/paste the “Selection Options” to be the same as the res.partner field’s selection options. 

This will pull the data from the res.partner model using the relation through partner_id. Now that field is available for you to use in your views. Just reference it as you would any other view. 

It’s that simple! 

I needed to add a selection for drug type in the model products.template so I opened the model by enabling debug mode, and going to settings/technical/models/products.template and created a new field called ‘x_schedule’. The data type is ‘selection’ and the selection options were as follows: 

[('none', 'None'), ('i', 'Schedule I'), ('ii', 'Schedule II'), ('iii', 'Schedule III'), ('iv', 'Schedule IV'), ('v', 'Schedule V'), ('legend', 'Legend')]

The next part is adding it to the view, so with debug mode still enabled, I went int to settings/technical/views and I create a new view called ‘[xxx] Product Additional Fields’ where any additional fields for products will go. 

View Type: ‘Form’

Object: ‘product.template’

Inherited View: ‘product.template.product.form’

View inheritance mode: ‘Extension View’

Under architecture add the following: 

<?xml version='1.0'?> <data>      <field name="invoice_policy" position="after">      <field name="x_schedule"/> </field>

</data>

I needed a filter that would show deliver orders that were due today or late. Here’s how I accomplished that:

<filter name="today" string="For Today" domain="[('state','in',('assigned', 'partially_available')),('min_date', '<=',datetime.datetime.now().strftime('%Y-%m-%d 23:23:59'))]" help="Pickings to be done today"/>

In the Sales/Reports/Sales view I needed the same thing, but just for sales today, not past. It is structured slightly differently: 

<filter name="today" string="For Today" domain="[('date', '>=',datetime.datetime.now().strftime('%Y-%m-%d 00:00:00'))]" help="Filter on  today"/>

I needed to change the label for a base field in Odoo 9 SA. If you try to change the label in the model it warns you that you should do that with python code or even better, by making a module. Being I’m on Odoo 9 SA (SaaS) I am not able to create modules. What I found you can do is create an extension view for that view and use the following: 

   <xpath expr="//field[@name='use_date']" position="attributes">        <attribute name="string">Beyond Use Date (BUD)</attribute>    </xpath>

The use case is this - you have a customer who has multiple shipping addresses and a single billing address. You send them invoices from Odoo but they require the billing address and the location to which the product they are paying for was shipped. 

This is something that plagued me for a while. It seems like it should be so simple, but it’s definitely not designed to be an immediate function. The issue is that there is no reference to the shipping address in the account.invoice model, and the only place that reference exists is in the sale.order model. However, there is no reference by ID to the sale.order record in the account.invoice model, only by reference which is a string such as “SO1234″. This means you have to look up the sales order by matching the reference string to the sales order name field. 

What I have found is somewhat of a hack, but it works! In the QWeb view for the account.invoice (account.report_invoice_document ) report add the following snippet where you want your address. 

<t t-if="o.origin">   <t t-set="order" t-value="request.env['sale.order'].search([('name', '=', o.origin)], limit=1)"/>   <t t-if="order">     <span t-field="order.partner_shipping_id" t-field-options="{"widget": "contact", "fields": ["address", "name", "phone", "fax"], "no_marker": true, "phone_icons": true}"/>   </t> </t>