project |
Project
Catalog: Odoo
Schema: project
The data in this table is partitioned per value of the column.
This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API.
Table Columns
The columns of the table project are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
---|---|---|---|---|
access_instruction_message |
string |
Access Instruction Message |
☐ |
|
access_token |
string |
Security Token |
☐ |
|
access_url |
string |
Portal Access URL |
☐ |
Customer Portal URL |
access_warning |
string |
Access warning |
☐ |
|
active |
boolean |
Active |
☐ |
If the active field is set to False, it will allow you to hide the project without removing it. |
activity_calendar_event_id_label |
string |
|
☐ |
|
activity_calendar_event_id |
string |
|
☐ |
|
activity_date_deadline |
datetime |
Next Activity Deadline |
☐ |
|
activity_exception_decoration |
string |
Activity Exception Decoration |
☐ |
Type of the exception activity on record. |
activity_exception_icon |
string |
Icon |
☐ |
Icon to indicate an exception activity. |
activity_ids |
string |
|
☐ |
|
activity_state |
string |
Activity State |
☐ |
Status based on activitiesOverdue: Due date is already passedToday: Activity date is todayPlanned: Future activities. |
activity_summary |
string |
Next Activity Summary |
☐ |
|
activity_type_icon |
string |
Activity Type Icon |
☐ |
Font awesome icon e.g. fa-tasks |
activity_type_id_label |
string |
|
☐ |
|
activity_type_id |
string |
|
☐ |
|
activity_user_id_label |
string |
|
☐ |
|
activity_user_id |
string |
|
☐ |
|
alias_bounced_content |
string |
Custom Bounced Message |
☐ |
If set, this content will automatically be sent out to unauthorized users instead of the default message. |
alias_contact |
string |
Alias Contact Security |
☑ |
Policy to post a message on the document using the mailgateway.- everyone: everyone can post- partners: only authenticated partners- followers: only followers of the related document or members of following channels |
alias_defaults |
string |
Default Values |
☑ |
A Python dictionary that will be evaluated to provide default values when creating new records for this alias. |
alias_domain |
string |
Alias domain |
☐ |
|
alias_enabled |
boolean |
Use Email Alias |
☐ |
|
alias_force_thread_id |
int32 |
Record Thread ID |
☐ |
Optional ID of a thread (record) to which all incoming messages will be attached, even if they did not reply to it. If set, this will disable the creation of new records completely. |
alias_id_label |
string |
|
☐ |
Internal email associated with this project. Incoming emails are automatically synchronized with Tasks (or optionally Issues if the Issue Tracker module is installed). |
alias_id |
string |
|
☐ |
Internal email associated with this project. Incoming emails are automatically synchronized with Tasks (or optionally Issues if the Issue Tracker module is installed). |
alias_model_id_label |
string |
|
☐ |
The model (Odoo Document Kind) to which this alias corresponds. Any incoming email that does not reply to an existing record will cause the creation of a new record of this model (e.g. a Project Task) |
alias_model_id |
string |
|
☐ |
The model (Odoo Document Kind) to which this alias corresponds. Any incoming email that does not reply to an existing record will cause the creation of a new record of this model (e.g. a Project Task) |
alias_name |
string |
Alias Name |
☐ |
The name of the email alias, e.g. 'jobs' if you want to catch emails for <jobs@example.odoo.com> |
alias_parent_model_id_label |
string |
|
☐ |
Parent model holding the alias. The model holding the alias reference is not necessarily the model given by alias_model_id (example: project (parent_model) and task (model)) |
alias_parent_model_id |
string |
|
☐ |
Parent model holding the alias. The model holding the alias reference is not necessarily the model given by alias_model_id (example: project (parent_model) and task (model)) |
alias_parent_thread_id |
int32 |
Parent Record Thread ID |
☐ |
ID of the parent record holding the alias (example: project holding the task creation alias) |
alias_status |
string |
Alias Status |
☐ |
Alias status assessed on the last message received. |
alias_user_id_label |
string |
|
☐ |
The owner of records created upon receiving emails on this alias. If this field is not set the system will attempt to find the right owner based on the sender (From) address, or will use the Administrator account if no system user is found for that address. |
alias_user_id |
string |
|
☐ |
The owner of records created upon receiving emails on this alias. If this field is not set the system will attempt to find the right owner based on the sender (From) address, or will use the Administrator account if no system user is found for that address. |
alias_value |
string |
Alias email |
☐ |
|
allocated_hours |
decimal |
Allocated Hours |
☐ |
|
allow_billable |
boolean |
Billable |
☐ |
|
allow_material |
boolean |
Products on Tasks |
☐ |
|
allow_milestones |
boolean |
Milestones |
☐ |
|
allow_quotations |
boolean |
Extra Quotations |
☐ |
|
allow_rating |
boolean |
Allow Customer Ratings |
☐ |
|
allow_recurring_tasks |
boolean |
Recurring Tasks |
☐ |
|
allow_subtasks |
boolean |
Sub-tasks |
☐ |
|
allow_task_dependencies |
boolean |
Task Dependencies |
☐ |
|
allow_timesheets |
boolean |
Timesheets |
☐ |
|
allow_worksheets |
boolean |
Worksheets |
☐ |
|
analytic_account_balance |
decimal |
Balance |
☐ |
|
analytic_account_id_label |
string |
|
☐ |
Analytic account to which this project, its tasks and its timesheets are linked. Track the costs and revenues of your project by setting this analytic account on your related documents (e.g. sales orders, invoices, purchase orders, vendor bills, expenses etc.).This analytic account can be changed on each task individually if necessary.An analytic account is required in order to use timesheets. |
analytic_account_id |
string |
|
☐ |
Analytic account to which this project, its tasks and its timesheets are linked. Track the costs and revenues of your project by setting this analytic account on your related documents (e.g. sales orders, invoices, purchase orders, vendor bills, expenses etc.).This analytic account can be changed on each task individually if necessary.An analytic account is required in order to use timesheets. |
assets_count |
int32 |
# Assets |
☐ |
|
billable_percentage |
int32 |
Billable Percentage |
☐ |
% of timesheets that are billable compared to the total number of timesheets linked to the AA of the project, rounded to the unit. |
bom_count |
int32 |
BoM Count |
☐ |
|
collaborator_count |
int32 |
# Collaborators |
☐ |
|
collaborator_ids |
string |
|
☐ |
|
color |
int32 |
Color Index |
☐ |
|
commercial_partner_id_label |
string |
|
☐ |
|
commercial_partner_id |
string |
|
☐ |
|
company_id_label |
string |
|
☐ |
|
company_id |
string |
|
☐ |
|
contracts_count |
int32 |
# Contracts |
☐ |
|
create_date |
datetime |
Created on |
☐ |
|
create_uid_label |
string |
|
☐ |
|
create_uid |
string |
|
☐ |
|
currency_id_label |
string |
|
☐ |
|
currency_id |
string |
|
☐ |
|
date_start |
datetime |
Start Date |
☐ |
|
date |
datetime |
Expiration Date |
☐ |
Date on which this project ends. The timeframe defined on the project is taken into account when viewing its planning. |
description |
string |
Description |
☐ |
Description to provide more information and context about this project |
display_create_order |
boolean |
Display Create Order |
☐ |
|
display_name |
string |
Display Name |
☐ |
|
doc_count |
int32 |
Number of documents attached |
☐ |
|
document_count |
int32 |
Number of documents in Project |
☐ |
|
documents_folder_id_label |
string |
|
☐ |
Workspace in which all of the documents of this project will be categorized. All of the attachments of your tasks will be automatically added as documents in this workspace as well. |
documents_folder_id |
string |
|
☐ |
Workspace in which all of the documents of this project will be categorized. All of the attachments of your tasks will be automatically added as documents in this workspace as well. |
documents_tag_ids |
string |
|
☐ |
|
encode_uom_in_days |
boolean |
Encode Uom In Days |
☐ |
|
expenses_count |
int32 |
# Expenses |
☐ |
|
favorite_user_ids |
string |
|
☐ |
|
has_any_so_to_invoice |
boolean |
Has SO to Invoice |
☐ |
|
has_any_so_with_nothing_to_invoice |
boolean |
Has a SO with an invoice status of No |
☐ |
|
has_message |
boolean |
Has Message |
☐ |
|
id |
int32 |
ID |
☐ |
|
invoice_count |
int32 |
Invoice Count |
☐ |
|
is_favorite |
boolean |
Show Project on Dashboard |
☐ |
|
is_fsm |
boolean |
Field Service |
☐ |
Display tasks in the Field Service module and allow planning with start/end dates. |
is_internal_project |
boolean |
Is Internal Project |
☐ |
|
is_milestone_exceeded |
boolean |
Is Milestone Exceeded |
☐ |
|
is_project_overtime |
boolean |
Project in Overtime |
☐ |
|
label_tasks |
string |
Use Tasks as |
☐ |
Name used to refer to the tasks of your project e.g. tasks, tickets, sprints, etc... |
last_update_color |
int32 |
Last Update Color |
☐ |
|
last_update_id_label |
string |
|
☐ |
|
last_update_id |
string |
|
☐ |
|
last_update_status |
string |
Last Update Status |
☑ |
|
message_attachment_count |
int32 |
Attachment Count |
☐ |
|
message_follower_ids |
string |
|
☐ |
|
message_has_error_counter |
int32 |
Number of errors |
☐ |
Number of messages with delivery error |
message_has_error |
boolean |
Message Delivery error |
☐ |
If checked, some messages have a delivery error. |
message_has_sms_error |
boolean |
SMS Delivery error |
☐ |
If checked, some messages have a delivery error. |
message_ids |
string |
|
☐ |
|
message_is_follower |
boolean |
Is Follower |
☐ |
|
message_main_attachment_id_label |
string |
|
☐ |
|
message_main_attachment_id |
string |
|
☐ |
|
message_needaction_counter |
int32 |
Number of Actions |
☐ |
Number of messages which requires an action |
message_needaction |
boolean |
Action Needed |
☐ |
If checked, new messages require your attention. |
message_partner_ids |
string |
|
☐ |
|
milestone_count_reached |
int32 |
Milestone Count Reached |
☐ |
|
milestone_count |
int32 |
Milestone Count |
☐ |
|
milestone_ids |
string |
|
☐ |
|
my_activity_date_deadline |
datetime |
My Activity Deadline |
☐ |
|
name |
string |
Name |
☑ |
Name of your project. It can be anything you want e.g. the name of a customer or a service. |
partner_email |
string |
☐ |
|
|
partner_id_label |
string |
|
☐ |
|
partner_id |
string |
|
☐ |
|
partner_phone |
string |
Phone |
☐ |
|
pricing_type |
string |
Pricing |
☐ |
The task rate is perfect if you would like to bill different services to different customers at different rates. The fixed rate is perfect if you bill a service at a fixed rate per hour or day worked regardless of the employee who performed it. The employee rate is preferable if your employees deliver the same service at a different rate. For instance, junior and senior consultants would deliver the same service (= consultancy), but at a different rate because of their level of seniority. |
privacy_visibility_warning |
string |
Privacy Visibility Warning |
☐ |
|
privacy_visibility |
string |
Visibility |
☑ |
People to whom this project and its tasks will be visible.- Invited internal users: when following a project, internal users will get access to all of its tasks without distinction. Otherwise, they will only get access to the specific tasks they are following.A user with the project > administrator access right level can still access this project and its tasks, even if they are not explicitly part of the followers.- All internal users: all internal users can access the project and all of its tasks without distinction.- Invited portal users and all internal users: all internal users can access the project and all of its tasks without distinction.When following a project, portal users will get access to all of its tasks without distinction. Otherwise, they will only get access to the specific tasks they are following.When a project is shared in read-only, the portal user is redirected to their portal. They can view the tasks, but not edit them.When a project is shared in edit, the portal user is redirected to the kanban and list views of the tasks. They can modify a selected number of fields on the tasks.In any case, an internal user with no project access rights can still access a task, provided that they are given the corresponding URL (and that they are part of the followers if the project is private). |
production_count |
int32 |
Manufacturing Orders Count |
☐ |
|
purchase_orders_count |
int32 |
# Purchase Orders |
☐ |
|
rating_active |
boolean |
Customer Ratings |
☐ |
|
rating_avg_percentage |
decimal |
Average Rating (%) |
☐ |
|
rating_avg |
decimal |
Average Rating |
☐ |
|
rating_count |
int32 |
# Ratings |
☐ |
|
rating_ids |
string |
|
☐ |
|
rating_percentage_satisfaction |
int32 |
Rating Satisfaction |
☐ |
Percentage of happy ratings |
rating_request_deadline |
datetime |
Rating Request Deadline |
☐ |
|
rating_status_period |
string |
Rating Frequency |
☑ |
|
rating_status |
string |
Customer Ratings Status |
☑ |
Collect feedback from your customers by sending them a rating request when a task enters a certain stage. To do so, define a rating email template on the corresponding stages.Rating when changing stage: an email will be automatically sent when the task reaches the stage on which the rating email template is set.Periodic rating: an email will be automatically sent at regular intervals as long as the task remains in the stage in which the rating email template is set. |
remaining_hours |
decimal |
Remaining Invoiced Time |
☐ |
|
resource_calendar_id_label |
string |
|
☐ |
|
resource_calendar_id |
string |
|
☐ |
|
sale_line_employee_ids |
string |
|
☐ |
Sales order item that will be selected by default on the timesheets of the corresponding employee. It bypasses the sales order item defined on the project and the task, and can be modified on each timesheet entry if necessary. In other words, it defines the rate at which an employee's time is billed based on their expertise, skills or experience, for instance.If you would like to bill the same service at a different rate, you need to create two separate sales order items as each sales order item can only have a single unit price at a time.You can also define the hourly company cost of your employees for their timesheets on this project specifically. It will bypass the timesheet cost set on the employee. |
sale_line_id_label |
string |
|
☐ |
Sales order item that will be selected by default on the tasks and timesheets of this project, except if the employee set on the timesheets is explicitely linked to another sales order item on the project.It can be modified on each task and timesheet entry individually if necessary. |
sale_line_id |
string |
|
☐ |
Sales order item that will be selected by default on the tasks and timesheets of this project, except if the employee set on the timesheets is explicitely linked to another sales order item on the project.It can be modified on each task and timesheet entry individually if necessary. |
sale_order_count |
int32 |
Sale Order Count |
☐ |
|
sale_order_id_label |
string |
|
☐ |
Sales order to which the project is linked. |
sale_order_id |
string |
|
☐ |
Sales order to which the project is linked. |
sequence |
int32 |
Sequence |
☐ |
|
shared_document_count |
int32 |
Shared Documents Count |
☐ |
|
shared_document_ids |
string |
|
☐ |
|
stage_id_label |
string |
|
☐ |
|
stage_id |
string |
|
☐ |
|
subscriptions_count |
int32 |
# Subscriptions |
☐ |
|
tag_ids |
string |
|
☐ |
|
task_count_with_subtasks |
int32 |
Task Count With Subtasks |
☐ |
|
task_count |
int32 |
Task Count |
☐ |
|
task_ids |
string |
|
☐ |
|
task_properties_definition |
string |
Task Properties |
☐ |
|
tasks |
string |
|
☐ |
|
timesheet_count |
int32 |
Timesheet Count |
☐ |
|
timesheet_encode_uom_id_label |
string |
|
☐ |
|
timesheet_encode_uom_id |
string |
|
☐ |
|
timesheet_ids |
string |
|
☐ |
|
timesheet_product_id_label |
string |
|
☐ |
Service that will be used by default when invoicing the time spent on a task. It can be modified on each task individually by selecting a specific sales order item. |
timesheet_product_id |
string |
|
☐ |
Service that will be used by default when invoicing the time spent on a task. It can be modified on each task individually by selecting a specific sales order item. |
total_timesheet_time |
int32 |
Total Timesheet Time |
☐ |
Total number of time (in the proper UoM) recorded in the project, rounded to the unit. |
type_ids |
string |
|
☐ |
|
update_ids |
string |
|
☐ |
|
use_documents |
boolean |
Documents |
☐ |
|
user_id_label |
string |
|
☐ |
|
user_id |
string |
|
☐ |
|
vendor_bill_count |
int32 |
Vendor Bill Count |
☐ |
|
warning_employee_rate |
boolean |
Warning Employee Rate |
☐ |
|
website_message_ids |
string |
|
☐ |
Website communication history |
workorder_count |
int32 |
Work Order Count |
☐ |
|
worksheet_template_id_label |
string |
|
☐ |
|
worksheet_template_id |
string |
|
☐ |
|
write_date |
datetime |
Last Updated on |
☐ |
|
write_uid_label |
string |
|
☐ |
|
write_uid |
string |
|
☐ |
|
01-03-2023 15:29 Version 22.1.135-BETA+3826