Toggle navigation

Data Files

Flectra is greatly data-driven, and a big part of modules definition is thus the definition of the various records it manages: UI (menus and views), security (access rights and access rules), reports and plain data are all defined via records.


The main way to define data in Flectra is via XML data files: The broad structure of an XML data file is the following:

  • Any number of operation elements within the root element flectra
<!-- the root elements of the data file -->
<?xml version="1.0" encoding="UTF-8"?>

Data files are executed sequentially, operations can only refer to the result of operations defined previously

Core operations


record appropriately defines or updates a database record, it has the following attributes:

model (required)
name of the model to create (or update)

the external identifier for this record. It is strongly recommended to provide one

  • for record creation, allows subsequent definitions to either modify or refer to this record
  • for record modification, the record to modify
context to use when creating the record

in update mode whether the record should be created if it doesn’t exist

Requires an external id, defaults to True.


Each record can be composed of field tags, defining values to set when creating the record. A record with no field will use all default values (creation) or do nothing (update).

A field has a mandatory name attribute, the name of the field to set, and various methods to define the value itself:

if no value is provided for the field, an implicit False will be set on the field. Can be used to clear a field, or avoid using a default value for the field.

for relational fields, should be a domain on the field’s model.

Will evaluate the domain, search the field’s model using it and set the search’s result as the field’s value. Will only use the first result if the field is a Many2one


if a ref attribute is provided, its value must be a valid external id, which will be looked up and set as the field’s value.

Mostly for Many2one and Reference fields


if a type attribute is provided, it is used to interpret and convert the field’s content. The field’s content can be provided through an external file using the file attribute, or through the node’s body.

Available types are:

xml, html
extracts the field’s children as a single document, evaluates any external id specified with the form %(external_id)s. %% can be used to output actual % signs.
ensures that the field content is a valid file path in the current model, saves the pair module,path as the field value
sets the field content directly as the field’s value without alterations
base64-encodes the field’s content, useful combined with the file attribute to load e.g. image data into attachments
converts the field’s content to an integer and sets it as the field’s value
converts the field’s content to a float and sets it as the field’s value
list, tuple
should contain any number of value elements with the same properties as field, each element resolves to an item of a generated tuple or list, and the generated collection is set as the field’s value

for cases where the previous methods are unsuitable, the eval attributes simply evaluates whatever Python expression it is provided and sets the result as the field’s value.

The evaluation context contains various modules (time, datetime, timedelta, relativedelta), a function to resolve external identifiers (ref) and the model object for the current field if applicable (obj)


The delete tag can remove any number of records previously defined. It has the following attributes:

model (required)
the model in which a specified record should be deleted
the external id of a record to remove
a domain to find records of the model to remove

id and search are exclusive


The function tag calls a method on a model, with provided parameters. It has two mandatory parameters model and name specifying respectively the model and the name of the method to call.

Parameters can be provided using eval (should evaluate to a sequence of parameters to call the method with) or value elements (see list values).

    <data noupdate="1">
        <record name="partner_1" model="res.partner">
            <field name="name">Odude</field>

        <function model="res.partner" name="send_inscription_notice"
            eval="[[ref('partner_1'), ref('partner_2')]]"/>

        <function model="res.users" name="send_vip_inscription_notice">
            <function eval="[[('vip','=',True)]]" model="res.partner" name="search"/>

    <record id="model_form_view" model="ir.ui.view">



Because some important structural models of Flectra are complex and involved, data files provide shorter alternatives to defining them using record tags:


Creates a QWeb view requiring only the arch section of the view, and allowing a few optional attributes:

the view’s external identifier
name, inherit_id, priority
same as the corresponding field on ir.ui.view (nb: inherit_id should be an external identifier)
if set to True and combined with a inherit_id, defines the view as a primary
comma-separated list of group external identifiers
if set to "True", the template is a website page (linkable to, deletable)
enabled or disabled, whether the view can be disabled (in the website interface) and its default status. If unset, the view is always enabled.

CSV data files

XML data files are flexible and self-descriptive, but very verbose when creating a number of simple records of the same model in bulk.

For this case, data files can also use csv, this is often the case for access rights:

  • the file name is model_name.csv
  • the first row lists the fields to write, with the special field id for external identifiers (used for creation or update)
  • each row thereafter creates a new record

Here’s the first lines of the data file defining US states

state_au_1,au,"Australian Capital Territory","ACT"
state_au_2,au,"New South Wales","NSW"
state_au_3,au,"Northern Territory","NT"
state_au_5,au,"South Australia","SA"
state_au_8,au,"Western Australia","WA"

rendered in a more readable format:

state_au_1auAustralian Capital TerritoryACT
state_au_2auNew South WalesNSW
state_au_3auNorthern TerritoryNT
state_au_5auSouth AustraliaSA
state_au_8auWestern AustraliaWA

For each row (record):

  • the first column is the external id of the record to create or update
  • the second column is the external id of the country object to link to (country objects must have been defined beforehand)
  • the third column is the name field for
  • the fourth column is the code field for