Here’s a sneak peak at the improvements that landed during the last month.
Changes for the User
To shipments we’ve added a field that calculates the total weight of the packages.
It is now possible to configure which units are used for the shipment volume and weight (instead of the hard coded values).
The clients now have an upper limit when counting records. They also use a human readable format for the count to a precision of 4 figures, and now display the number of record selected as well.
Users can now configure for each view which optional columns to display.
All the list views have been reviewed to add or mark optional columns and provide a simplified version by default.
The model, field and column is now displayed in the import error message. This makes it easier for the user to find mistakes in a CSV file.
Tryton now also searches for the BIC when searching by bank name. And when searching bank account numbers, it only searches for the starting number.
We added a test to reconcile all the lines when running the reconcile account wizard. This ensures this special case is always found even if the number of lines is greater than the reconciliation chunk.
The general ledger now hides the debit/credit columns if there are no lines for the period. And by default the list opens with only the accounts that contains lines.
A default statement journal is created automatically when the account_statement module is activated. This eases on-boarding new users.
When searching for a payment to link to a statement line, Tryton displays first the payment with the closest amount.
The chart of account now forces child accounts to have the same type as the parent account (if it has one).
Tryton now supports the Shopify webhook which allows orders to be updated as soon as the event happens (instead of needing to wait for the scheduled task).
The SIREN and SIRET numbers are now stored as party identifiers. And an identifier can be linked to an address in the same way as SIRET.
We now raise a warning when validating a supplier invoice that has the same reference as another invoice.
It is now forbidden to decrease the number of digits of a unit of measure. This was needed to prevent validation errors on existing records that use that unit of measure.
New Modules
The Account Invoice Watermark Module adds a draft or paid watermark to the printed invoice.
The Account Tax Non-Deductible Module allows defining non-deductible taxes and reporting them.
The Sale Invoice Date Module fills in the invoice date for invoices created by sales. The invoice date is used for grouping, allowing invoices to be generated based on a period (i.e: for Monthly Invoices).
Changes for the Developer
We support limit and offset to ModelSQL count search and search_count. The ORM optimizes the query to avoid reading unnecessary records when the limit is smaller than the number of records in the table.
We improved the parsing in the get_eval_fields function to be 60% faster.
The desktop client uses, by default, UTF-8 with BOM for the CSV import/export.
The domain of a Reference field is now a dictionary which contains a separate domain for each target model.
The order of unsorted Selection fields is now based on the index of the field definition. For example ordering sales by the state field, will put drafts first, then quotations, etc.
The server retries by default 5 times on temporary SMTP server errors.
We replaced the ilike operator on Reference fields by a simple like. This may allow the database engine to use indexes.