Skip to Content
Odoo Menu
  • Log ind
  • Prøv gratis
  • Apps
    Økonomi
    • Bogføring
    • Fakturering
    • Udgifter
    • Regneark (BI)
    • Dokumenter
    • e-Signatur
    Salg
    • CRM
    • Salg
    • POS Butik
    • POS Restaurant
    • Abonnementer
    • Udlejning
    Hjemmeside
    • Hjemmesidebygger
    • e-Handel
    • Blog
    • Forum
    • LiveChat
    • e-Læring
    Forsyningskæde
    • Lagerbeholdning
    • Produktion
    • PLM
    • Indkøb
    • Vedligeholdelse
    • Kvalitet
    HR
    • Medarbejdere
    • Rekruttering
    • Fravær
    • Medarbejdersamtaler
    • Anbefalinger
    • Flåde
    Marketing
    • Markedsføring på sociale medier
    • E-mailmarketing
    • SMS-marketing
    • Arrangementer
    • Automatiseret marketing
    • Spørgeundersøgelser
    Tjenester
    • Projekt
    • Timesedler
    • Udkørende Service
    • Kundeservice
    • Planlægning
    • Aftaler
    Produktivitet
    • Dialog
    • Godkendelser
    • IoT
    • VoIP
    • Vidensdeling
    • WhatsApp
    Tredjepartsapps Odoo Studio Odoo Cloud-platform
  • Brancher
    Detailhandel
    • Boghandel
    • Tøjforretning
    • Møbelforretning
    • Dagligvarebutik
    • Byggemarked
    • Legetøjsforretning
    Mad og værtsskab
    • Bar og pub
    • Restaurant
    • Fastfood
    • Gæstehus
    • Drikkevareforhandler
    • Hotel
    Ejendom
    • Ejendomsmægler
    • Arkitektfirma
    • Byggeri
    • Ejendomsadministration
    • Havearbejde
    • Boligejerforening
    Rådgivning
    • Regnskabsfirma
    • Odoo-partner
    • Marketingbureau
    • Advokatfirma
    • Rekruttering
    • Audit & certificering
    Produktion
    • Tekstil
    • Metal
    • Møbler
    • Fødevareproduktion
    • Bryggeri
    • Firmagave
    Heldbred & Fitness
    • Sportsklub
    • Optiker
    • Fitnesscenter
    • Kosmetolog
    • Apotek
    • Frisør
    Håndværk
    • Handyman
    • IT-hardware og support
    • Solenergisystemer
    • Skomager
    • Rengøringsservicer
    • VVS- og ventilationsservice
    Andet
    • Nonprofitorganisation
    • Miljøagentur
    • Udlejning af billboards
    • Fotografi
    • Cykeludlejning
    • Softwareforhandler
    Gennemse alle brancher
  • Community
    Få mere at vide
    • Tutorials
    • Dokumentation
    • Certificeringer
    • Oplæring
    • Blog
    • Podcast
    Bliv klogere
    • Udannelselsesprogram
    • Scale Up!-virksomhedsspillet
    • Besøg Odoo
    Få softwaren
    • Download
    • Sammenlign versioner
    • Udgaver
    Samarbejde
    • Github
    • Forum
    • Arrangementer
    • Oversættelser
    • Bliv partner
    • Tjenester til partnere
    • Registrér dit regnskabsfirma
    Modtag tjenester
    • Find en partner
    • Find en bogholder
    • Kontakt en rådgiver
    • Implementeringstjenester
    • Kundereferencer
    • Support
    • Opgraderinger
    Github Youtube Twitter LinkedIn Instagram Facebook Spotify
    +1 (650) 691-3277
    Få en demo
  • Prissætning
  • Hjælp

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

  • CRM
  • e-Commerce
  • Bogføring
  • Lager
  • PoS
  • Projekt
  • MRP
All apps
Du skal være registreret for at interagere med fællesskabet.
All Posts People Emblemer
Tags (View all)
odoo accounting v14 pos v15
Om dette forum
Du skal være registreret for at interagere med fællesskabet.
All Posts People Emblemer
Tags (View all)
odoo accounting v14 pos v15
Om dette forum
Hjælp

How to add a "product" field to a project issue?

Tilmeld

Få besked, når der er aktivitet på dette indlæg

Dette spørgsmål er blevet anmeldt
fieldcustommodelissue
2 Besvarelser
7088 Visninger
Avatar
Martin

I have defined a new model "bicycle" for a virtual bicycle factory. Every bicycle has a frame number, type etc. When a customer calls, who has an issue with one or more bicycles, I like to add references in the issue to the bicycles by referencing the affected bicycles in the project issue form. An issue can be about zero or more bicycles, and a bicycle can have zero or more issues.

How would I implement this?

What is the correct type of the new field in the project issue model? one2many or many2many or something else? Do I need to do sth. in the XML view to prevent creation of a new bicycle object from the project issue? I want only reference bicycles already existing in the database. When I add a one2many field x_bicycle in the project issue table and use a <field name="x_bicycle"/> in the project issue form view, I get the following error:

ProgrammingError: operator does not exist: character varying = integer
LINE 1: ....id FROM "bicycle" WHERE ("bicycle"."framenumber" in (2)) OR...
                                                             ^
HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.

What am I doing wrong? Thanks in advance!

This is bicycle.py:

from osv import fields, osv
import time

class bicycle(osv.osv):
    _name = "bicycle"
    _description = "Bicycle"
    _rec_name = "framenumber"
    _columns = {
        'framenumber': fields.char('Frame Number', size=7, required=True),
        'mechanic': fields.char('Mechanic Acronym', size=20),
        'productiondt': fields.datetime('Date/Time of Production'),
        'type': fields.selection(
            [('C', 'City Bicycle'),
             ('R', 'Road Bicycle'),
             ('T', 'Touring Bicycle'),
             ('F', 'Folding Bicycle')],
            'Type'),
        'framerevision': fields.selection(
            [('A', 'Revision A'),
             ('B', 'Revision B')],
            'Frame Revision'),
        }

    _sql_constraints = [
        ('framenumber_uniq', 'unique (framenumber)', 'The frame number must be unique!')
        ]

bicycle()

This is bicycle_view.xml:

<?xml version="1.0" encoding="utf-8"?>
<openerp>
    <data>
        <record model="ir.ui.view" id="bicycle_tree_view">
            <field name="name">bicycle.tree</field>
            <field name="model">bicycle</field>
            <field name="type">tree</field>
            <field name="arch" type="xml">
                <tree string="Bicycle">
                    <field name="framenumber"/>
                    <field name="type"/>
                    <field name="framerevision"/>
                    <field name="mechanic"/>
                </tree>
            </field>
        </record>

        <record model="ir.ui.view" id="bicycle_form_view">
            <field name="name">bicycle.form</field>
            <field name="model">bicycle</field>
            <field name="type">form</field>
            <field name="arch" type="xml">
                <form string="Bicycle">
                    <field name="framenumber"/>
                    <field name="type"/>
                    <field name="framerevision"/>
                    <field name="mechanic"/>
                </form>
            </field>
        </record>

        <record model="ir.actions.act_window" id="action_bicycle_form">
            <field name="name">bicycle</field>
            <field name="res_model">bicycle</field>
        </record>

        <menuitem name="Bicycle"
          parent="project.menu_project_management"
          id="bicycle_menu_mainform" action="action_bicycle_form"/>
    </data>
</openerp>
2
Avatar
Kassér
Avatar
Martin
Forfatter Bedste svar

It seems, that the right field type for pointing from project issues to bicycles is many2many. It works mainly as I want it, with some minor UI issues to work on.

0
Avatar
Kassér
Avatar
Ali Ravani
Bedste svar

you should use one2many fields.. which will show all the fields in form and tree view both...

0
Avatar
Kassér
Martin
Forfatter

Thanks, but this did not work for me. I rephrased my question and added some code to make clear, what I like to do.

Enjoying the discussion? Don't just read, join in!

Create an account today to enjoy exclusive features and engage with our awesome community!

Tilmeld dig
Related Posts Besvarelser Visninger Aktivitet
How can I mark a field "unique" in a custom model? Løst
field custom unique model
Avatar
Avatar
Avatar
Avatar
3
sep. 24
48112
add an existing field to a model
field custom state model
Avatar
Avatar
1
mar. 15
7887
Custom model - avoid deleting values when in use Løst
custom model
Avatar
Avatar
2
mar. 22
3558
what's the field '_date_name' means in a model
field model
Avatar
0
mar. 24
4229
Field referring to the same model?
field custom related model same
Avatar
Avatar
3
jun. 17
7774
Community
  • Tutorials
  • Dokumentation
  • Forum
Open Source
  • Download
  • Github
  • Runbot
  • Oversættelser
Tjenester
  • Odoo.sh-hosting
  • Support
  • Opgradere
  • Individuelt tilpasset udvikling
  • Uddannelse
  • Find en bogholder
  • Find en partner
  • Bliv partner
Om os
  • Vores virksomhed
  • Brandaktiver
  • Kontakt os
  • Stillinger
  • Arrangementer
  • Podcast
  • Blog
  • Kunder
  • Juridiske dokumenter • Privatlivspolitik
  • Sikkerhedspolitik
الْعَرَبيّة Català 简体中文 繁體中文 (台灣) Čeština Dansk Nederlands English Suomi Français Deutsch हिंदी Bahasa Indonesia Italiano 日本語 한국어 (KR) Lietuvių kalba Język polski Português (BR) română русский язык Slovenský jazyk slovenščina Español (América Latina) Español ภาษาไทย Türkçe українська Tiếng Việt

Odoo er en samling open source-forretningsapps, der dækker alle dine virksomhedsbehov – lige fra CRM, e-handel og bogføring til lagerstyring, POS, projektledelse og meget mere.

Det unikke ved Odoo er, at systemet både er brugervenligt og fuldt integreret.

Website made with

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now