# Newsletter September 2019

**URL:** https://discuss.tryton.org/t/newsletter-september-2019/1634
**Category:** News
**Created:** [September 1, 2019, 6:00am UTC](https://discuss.tryton.org/t/newsletter-september-2019/1634 "2019-09-01T06:00:06Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [September 1, 2019, 6:00am UTC](https://discuss.tryton.org/t/newsletter-september-2019/1634/1 "2019-09-01T06:00:06Z")

</div>

![White Wall Paint Hallway](https://discuss-cdn.tryton.org/uploads/default/original/1X/db16bd1050a569d0dd377d6c4e5c76940d1ad726.jpeg)

For this coming back month, Tryton has still improved for the users by simplifying some usage but also for the developers by providing more tools.

Contents:

- [Changes for users](#heading--users)
- [Changes for developers](#heading--developers)

## Changes For The User

The [mobile contacts can now be clicked](https://bugs.tryton.org/issue8544) similar to phone contacts.  
The [update unite price](https://bugs.tryton.org/issue7862) flag of taxes is now also supported on children taxes.

In addition to the country, the [tax rules can now be written using the subdivisions](https://bugs.tryton.org/issue8252) of origin and/or destination. A child subdivision will match the rule based on an upper level subdivision. This is useful for countries that have different tax rates for some subdivisions.

It is now possible to define [default values for the customer and supplier tax rules](https://bugs.tryton.org/issue8542). This can be useful to apply a local tax rule based on subdivision by default.

Now it is possible to configure a [sequence for the product code](https://bugs.tryton.org/issue8545) that will be used to be filled at creation time. This may be used to ensure to have a unique code per product, even when it is duplicated.

The product [cost price can be used in the price list](https://bugs.tryton.org/issue8467). It uses the cost price of the company set in the context. This allows to build price lists by defining a margin to apply on the cost.

It is now possible to configure the [customer code](https://bugs.tryton.org/issue5812) of the current company on the supplier party. The code will be displayed on the [request for quotation](https://en.wikipedia.org/wiki/Request_for_quotation).

## Changes For The Developer

We added a [partial support of TO\_CHAR](https://bugs.tryton.org/issue8464) for date and datetime for SQLite Databases. We manage to support only the date and datetime which are the most useful usage and only for formats that can be easily converted into python strftime format. So we can use it now without breaking tests on SQLite.

We [added a new function on `Report` to format timedelta](https://bugs.tryton.org/issue7443). It uses the same representation as the clients to format _duration_ field values.

As we now keep a link between the inventory moves and the outgoing moves, we can [simplify the synchronization algorithm](https://bugs.tryton.org/issue8363) to use this link. Another advantage is that if the product is changed on the inventory move, the outgoing move is also updated instead of creating a new move.

If you forget to set a context on your RPC calls, Tryton will [raise a better error message](https://bugs.tryton.org/issue8565).

Now we have a [`lazy_gettext` method](https://bugs.tryton.org/issue8560) which allows to defer the translation by using a `LazyString`. It can be used as [label or help text of `Fields`](http://docs.tryton.org/projects/server/en/latest/ref/models/fields.html#field-options). This is useful for base `Model` classes and [`Mixins`](https://en.wikipedia.org/wiki/Mixin) to limit the duplication of the translation of the same string for each derived class.