ray-odoo

Current Versions

Major Version	SaaS Version	Official Release Date	Planned End of life	Bug fix	New On Premise	New Odoo Online	New Odoo.sh
16.0		October 12th 2022	Q4 2025	✅	✅	🔴	✅
	saas-16.1	February 2023	June 2023	🔴	🔴	🔴	🔴
	saas-16.2	March 2023	Q4 2023	🔴	🔴	🔴	🔴
	saas-16.3	June 2023	Q4 2023	🔴	:red_circ

ray-odoo

SEARCH VIEW:

<data>

<field name="product_id" position="after">
    <field name="name"/>
</field>    

<field name="partner_id" position="after">
    <field name="date_planned"/>

ray-odoo

# Odoo 16/17/18 - ray

###################
# create a record #
###################
rec = env[''].create({})
env['ir.model.data'].create({'model': '','module': 'ray_odoo_script','name': '', 'res_id': rec.id})


##############################

ray-odoo

# custom_ray_odoo

distance = 50
delivery_address = record.partner_shipping_id or record.partner_id

lat = delivery_address.partner_latitude
lng = delivery_address.partner_longitude

if lat == 0.0 or lng == 0.0:
  raise UserError("Customer Address has not been geocoded!")

ray-odoo

<data>

<xpath expr="//notebook/page[@name='operations']/field[@name='move_ids_without_package']/tree/field[@name='product_uom_qty']" 
       position="after">
       
  <field name="x_calc_quantity" 
         column_invisible="1"/>
  
  <field name="x_gross_quantity" 
         column_invisible="parent.picking_type_code != 'incoming' or (parent.state != 'assigned' and parent.state !='done')"/>

ray-odoo

<data>
    
<t t-esc="record.scheduled_date.value and record.scheduled_date.value.split(' ')[0] or False" 
   position="before">
  <button name="671" 
          icon="fa-calendar-minus-o" 
          type="action"/>
</t>

<t t-esc="record.scheduled_date.value and record.scheduled_date.value.split(' ')[0] or False" 

ray-odoo

# custom_ray_odoo

# loop through all selected product(s)
for record in records:
    
    # set lead time to default 3 days
    lead_time = 3
    found_vendor = False
    
    # loop through all the vendor(s) on the purchase tab

ray-odoo

Bank Balances Clearing: (debit balance if positive, credit balance if negative)
Statement Balance - credit BB clearing, debit the outstanding receipts account
OR
Statement Balance - debit BB clearing, credit the outstanding payments account

There will be debits left in the BB clearing, based on uncleared Customer deposits
credit BB clearing, debit the outstanding receipts account

There will be credits left in the BB clearing, based on uncleared Vendor payments
debit BB clearing, credit to outstanding payments

ray-odoo

<tree multi_edit="1" create="0">
  <field name="company_id" invisible="1"/>
  <field name="bom_id" readonly="1"/>
  <field name="product_id" context="{'default_detailed_type': 'product'}"/>
  <field name="product_tmpl_id" invisible="1"/>
  <button name="action_see_attachments" type="object" icon="fa-files-o" aria-label="Product Attachments" 
          title="Product Attachments" class="float-end"/>
  <field name="attachments_count" class="text-start" string=" "/>
  <field name="product_qty"/>
  <field name="product_uom_category_id" invisible="1"/>

ray-odoo

1) Setup two CC Journals with related accounts - via Add Bank Account
- one is for a single card holder
- one is for a corporate card with many card holders - modeled as payment methods with the top being "Select a Card"

2) Create a custom field x_payment_method_line_id on account.move.line

It is a many2one to account.payment.method.line

Related: move_id.payment_id.payment_method_line_id