Forms | Data API

by
Odoo
v 14.0 Third Party 500
Download for v 14.0 Deploy on Odoo.sh Live Preview
Included Dependencies
Lines of code 5934
Technical Name formio_data_api
LicenseLGPL-3
Websitehttps://www.novacode.nl
Also available in version v 12.0 v 13.0 v 11.0
You bought this module and need support? Click here!
Included Dependencies
Lines of code 5934
Technical Name formio_data_api
LicenseLGPL-3
Websitehttps://www.novacode.nl
Also available in version v 12.0 v 13.0 v 11.0

Forms | Data API

Python API for Forms data (builder, form/submission)

Installation Requirements
  • PyPi package formio-data (version >= 0.3.6)
    - Install: pip3 install -U formio-data
    - GitHub project: https://github.com/novacode-nl/python-formio-data

User Documentation

User Documentation is available on the GitHub Wiki

https://github.com/novacode-nl/odoo-formio/wiki

Visit the online Demo

Click the Live Preview button in the top.

Users (email / password)

  • demo / demo
  • portal / portal

Releases

1.4

  • Fix formio.form language determination in __getattr__ which gets the (Python) formiodata Form object.

1.3

  • Renaming (v1.2) ETL API implementation and usage (prefixes):
    - FROM: server_value_api
    - TO: server_api
    (!!) This is backwards incompatible and requires to change existing Form Builders which apply this feature since v1.2.

1.2

  • New ETL API feature: Get and set Component Value by Server (Python) Code.

1.1

  • Add global noupdate_form rule in component ETL API. This replaces res_field_noupdate_form, introduced in version 1.0.

1.0

  • MAJOR IMPROVEMENT of the component ETL API, to load and prefill data from Odoo field(s).
    This is a major change that greatly improves ease of use, flexibility and new features to come.
    The previous API/usage (in Property Name, aka the component key) is still supported, but deprecated and logs a DEPRECATION warning.

0.9

  • Pass determined (lang) date_format and time_format to the Form object contructor.

0.8

  • New ETL API: OdooUser
    ETL a field from current user into the Form.
    (could also be read as the logged-in user)
  • Change ETL API: Odoo
    This now ETL a field from the Resource model object into the Form, also when Form has state = DRAFT.
  • Change ETL API: OdooModel
    ETL a field from the linked Resource model object into the Form.
    (!!) This is backwards incompatible and requires to change existing Form Builders to: OdooModel__model

0.7

  • Fix/change due to recent change in the Python formiodata library (version: 0.3.0)
    Change (formiodata) Builder object attr: form_components became input_components

0.6

  • New API feature, support for Mail Template:
    Form model object (formio.form) can now be used in a Mail Template (Jinja template renderer), e.g. to show field value, select choices etc.
    This extends the Mail Render Mixin, because the Jinja Sandbox object doesn't directly allow ${object._formio}, which it treats as unsafe and throws an exception.

    USAGE EXAMPLE (where object is a formio.form model object):
    ${formio(object).input.firstName.value}

0.5

  • Remove silly model determination by initial_res_model_id. The current model is always stored and present in res_model_id.

0.4

  • New API feature OdooModel
    ETL the Odoo model name into Forms (API Property Name: OdooModel).

0.3

  • Change ETL Odoo field-data (API): field delimter from "." to "__" (2 underscores).
    - A dot "." results in undesired submission data, due to the formio Javascript library/API. - A dash is allowed, however causing issues with the ETL module (formio_etl).

0.2

  • New API features Odoo and OdooRF
    ETL Odoo field-data into Forms.

0.1

  • Initial version

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.