- Mailing Lists
- Contributors
- [26137] Usage of Py3o templating engine in Odoo projects
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
[26137] Usage of Py3o templating engine in Odoo projects
Dear contributors,
we wanted to have the ability to generate sales and invoice documents
based on document templates in one of our Odoo projects.
For this purpose, we decided to give the template engine Py3o a try. In
the end, we came up with some questions
we would like to ask you.
* Have you been able to realize a similar workflow compared to the
application Microsoft Sharepoint? If that is the case, how did you do this?
* What means did you use the store the data Py3o needs to access during
filling the template?
* In which way did you store an already generated generated report?
We are looking forward to your feedback and thank you for this in advance.
Best regards,
Manuel
--
Mit freundlichen Grüßen
Manuel Engel
Trainee Anwendungsentwicklung
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
Phone: +49 4105 56156-22
Fax: +49 4105 56156-10
Email: manuel.engel@initos.com
Web: http://www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr: DE815580155
by Manuel Engel - 02:15 - 2 Oct 2020
Follow-Ups
-
Re: [26137] Usage of Py3o templating engine in Odoo projects
Thanks Manuel, to clarify the questions at stake of my colleague a bit more precise: An ERP-System is meant to be the single source of truth. That's why we we would ideally retain all the structured data components (e.g. price, uom,...) that go into a Py3o report in the first place parsed back in the ERP-system (of course with changed content if it got changed in the Word / LibreOffice world). Actually this is what Sharepoint is trying to cover. So our questions are: Are there use cases out there that use Py3o to generate odt documents, let the user manipulate its content in a visual way and store back at least the structured part of the information "on safe" in the system and if yes where an how? For now and for us Py3o is seems to be too clumsy for that and the technical challenges to solve too vast so that we can hardly imagine that somebody ever tried to use it in such a use case, but we are definitely eager to know and would love to hear about alternatives. An no doing the entire unstructured part of a potential report document in 1..n text field in the Odoo backend isn't a really god idea either, we think. Best Frederik Am Freitag, den 02.10.2020, 12:16 +0000 schrieb Manuel Engel: > Dear contributors, > we wanted to have the ability to generate sales and invoice > documents > based on document templates in one of our Odoo projects. > For this purpose, we decided to give the template engine Py3o a try. > In > the end, we came up with some questions > we would like to ask you. > > > * Have you been able to realize a similar workflow compared to the > application Microsoft Sharepoint? If that is the case, how did you do > this? > * What means did you use the store the data Py3o needs to access > during > filling the template? > * In which way did you store an already generated generated report? > > We are looking forward to your feedback and thank you for this in > advance. > > Best regards, > Manuel > > > -- > Mit freundlichen Grüßen > > Manuel Engel > Trainee Anwendungsentwicklung > > > initOS GmbH > An der Eisenbahn 1 > 21224 Rosengarten > > Phone: +49 4105 56156-22 > Fax: +49 4105 56156-10 > > Email: manuel.engel@initos.com > Web: http://www.initos.com > > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > > Sitz der Gesellschaft: Rosengarten – Klecken > Amtsgericht Tostedt, HRB 205226 > Steuer-Nr: 15/200/53247 > USt-IdNr: DE815580155 > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 03:26 - 2 Oct 2020