Tryton vs. ERPnext

[udono]

Thank you @htgoebel for your comparison.

For the Tryton side I would like to share some additional information.

@htgoebel

E.g. ERPnext has quite some functions (“onboarding”) making it easy to get started and testing, whereas in Tryton such wizards are rejected since there are other (manual) means to achieve the result.

The first-install-wizards infrastructure in Tryton is already in use in several modules:

• Create User
• Create company
• Create chart of accounts

Also we have separated user configurations for every functional topic. And don’t forget to participate our Blank State and Onboarding discussion.

@htgoebel

E.g. you can easy customize reports by simple dragging “variables” to the right place.

In Tryton you can customise most reports with LibreOffice or an text editor.

@htgoebel

This not only imposes quite some problems when changing entries, but also is slow and increases storage and memory consumption. The later is esp. true, since every table contains a “modified-by” and “owner” user-id as a string.

Tryton also uses these fields for every table:

• id as primary key,
• create-uid,
• create_date,
• write-uid,
• write_date

but we use integer for id and uid and timestamp(6) for the dates. id has default database INDEX and uses sequences. The uid refers to the res_user table, but is not JOINT for some reasons, but Tryton disallows the deletion of res_user entries.

@htgoebel

…which is a thread to GDPR compliance.

Please become part of our GDPR discussion. E.g. Art. 17 of the GDPR in Tryton is addressed with the possibility to Erase parties at any time. The deletion of a party is done by removing personal identifiable data in fields, but keeping the records to satisfy the existing relational data integrity.