Message Threads | The Odoo Community Association

IDP initiate with SAML

Hi all,

We are working on IDP Initiated flow with SAML auth.
Someone did a similar flow?

Found this related OCA module:
https://github.com/OCA/server-auth/blob/16.0/auth_saml/README.rst

--

by Hed Shefer - 02:50 - 27 Oct 2024

Re: recurring payments

Hi Jan,

My team is acctually working on this now, we'll do a pr for v16 probably next week, i'll be happy to share the link when we upload, tests and reviews weolcomed.

Best,

On 10/25/2024 4:38 PM Jan Suhr | Nitrokey <notifications@odoo-community.org> wrote:

Hi!
I'm using OCA Contracts and am interested in recurring payments for 
these via Stripe or PayPal. As far as I know there is no such build-in 
feature for Community Edition. I found OCA's contract_payment_auto for 
10.0 [1] (PR for 12.0 [2]) which seems to do what I want, as well as a 
few paid modules which look incompatible with OCA's Contracts. I'm 
wondering what is the best approach to tackle this in 15.0. Would it be 
feasible to migrate contract_payment_auto to 15.0 or is there a good 
reason why this hasn't been done yet? Any better suggestion?

Best regards
Jan

[1] https://github.com/OCA/contract/tree/10.0/contract_payment_auto
[2] https://github.com/OCA/contract/pull/798

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Jorge Elena Poblet
CEO & Founder
Binhex
j.elena@binhex.cloud
Mobile (Spain) : +34 622 40 08 08
Mobile (USA): +1 561 403 4406

Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria

Start for free: Try Odoo Community in the cloud

This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy

by Jorge Elena Poblet - 05:50 - 25 Oct 2024

recurring payments

Hi!
I'm using OCA Contracts and am interested in recurring payments for 
these via Stripe or PayPal. As far as I know there is no such build-in 
feature for Community Edition. I found OCA's contract_payment_auto for 
10.0 [1] (PR for 12.0 [2]) which seems to do what I want, as well as a 
few paid modules which look incompatible with OCA's Contracts. I'm 
wondering what is the best approach to tackle this in 15.0. Would it be 
feasible to migrate contract_payment_auto to 15.0 or is there a good 
reason why this hasn't been done yet? Any better suggestion?

Best regards
Jan

[1] https://github.com/OCA/contract/tree/10.0/contract_payment_auto
[2] https://github.com/OCA/contract/pull/798

by Jan Suhr - 05:36 - 25 Oct 2024

Global Online Candidates OCA Delegates - Dating Show

Hello OCA members and OCA Delegates,

Today, Virginie and Tom hosted what I called the Candidates OCA Delegates Dating Show. They made sure everyone was given enough time to shine and share their views and opinions.

The online meeting reminded me of Steve Jobs hosting the Macintosh Software Dating Game with Bill Gates in 1983. It’s really fun to watch, especially with the '80s tunes and Steve Jobs' head-shaking enthusiasm.

Click the link below to watch the video:
https://youtu.be/j7WVrkJYXeI

All jokes aside, it was great to be part of the global online OCA meeting, from Japan to Argentina, and to witness the enthusiasm of all the candidates.

I don’t mind if the recording is shared with all OCA members and not just the OCA Delegates. Everyone can see how this process is executed, which certainly helps in attracting candidates for next year.

One last thing:
The OCA Board can make an exception this year and select all 18 candidates to help the OCA move forward faster. As Steve Jobs said in the video, I can’t choose one of you; I need all of you!

I had fun and really enjoyed the meeting, and I encourage other candidates, delegates, and hosts, to share their experiences of the “Dating Show.”

Warm regards,

Michel Stroom
Helping promote the OCA to get more members and sponsors

Remark / Note / P.S.:

I apologize in advance for sending this email to the contributors list. I really don’t know where else to send it, and I haven’t found an email address for only OCA members and delegates.

Idea:

Maybe we can implement the Odoo Forum app to set up different channels, like they already did at the local Spanish OCA.

==> If you’re not an OCA Member, You are welcome to Join us<==

Click the link below:

https://odoo-community.org/shop/24-msm-2024-oca-member-503809

by Michel Stroom - 05:31 - 23 Oct 2024

Re: Submmit an Odoo website form as an Iframe

V17

On Wed, 23 Oct 2024 at 17:58, Michel Stroom <notifications@odoo-community.org> wrote:

What is the Odoo version you are using?

On 23 Oct 2024, at 13:43, Hed Shefer <notifications@odoo-community.org> wrote:

Hi all,

I'm trying to embed an Odoo website form as an iframe and encountering a 400 error.
The original Odoo website form works well when not used in Iframe.

Tried to change csrf=False with no success, do you have other ideas?
--

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

by Hed Shefer - 05:21 - 23 Oct 2024

Re: Big number changed automatically on float fields

I reviewed this before. I think is the "why is happening?" I also make a research of github issues and even stackoverflow but it's not the same context. Almost every issue related comes from the misleading float_round in float_utils helpers but I'm not even working with a float directly I just have inserted a large number and it's just python dealing with it like a float **18, not Odoo ORM. I'll read again the documentation in search of some hint. Thanks.

On 10/23/24 10:37, Holger Brunn wrote:

https://docs.python.org/3/tutorial/floatingpoint.html


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Ing. Rolando Pérez Rebollo - 05:02 - 23 Oct 2024

Re: Submmit an Odoo website form as an Iframe

What is the Odoo version you are using?

On 23 Oct 2024, at 13:43, Hed Shefer <notifications@odoo-community.org> wrote:

Hi all,

I'm trying to embed an Odoo website form as an iframe and encountering a 400 error.
The original Odoo website form works well when not used in Iframe.

Tried to change csrf=False with no success, do you have other ideas?
--

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Michel Stroom - 04:56 - 23 Oct 2024

RE: Big number changed automatically on float fields

Dear,

In Python, you have a Decimal class. Here your numbers are stored in full. So maybe this is a solution.

With kind regards,

Van Hirtum Johan

Van: Rolando Pérez Rebollo [mailto:notifications@odoo-community.org]
Verzonden: woensdag 23 oktober 2024 16:43
Aan: Contributors
Onderwerp: Re: Big number changed automatically on float fields

> I'm interested in the business context of this problem. What kind of accounting are you doing where numbers have 19 digits?

It's a country with a very high inflation but the company operations really runs in USD so when converting from USD to local currency there are these kind of large numbers.

> A value with the last Nth digits changed.

For 1513372483569320000 is always the last five digits, the number stays the same till 15133724835693. My guess is due to the use of float for scientific notation the rest of the number gets messed up for some sort of global digit precision setting.

The columns in postgres that stores the values for credit and debit fields are of type numeric but without precision and scale settings. For me the responsible for the issue is python.

On 10/23/24 10:12, Janik von Rotz wrote:

Hi Rolando
I'm interested in the business context of this problem. What kind of accounting are you doing where numbers have 19 digits?
Your questions reminds me of the first Odoo Partner Days. Somebody asked something similar in the context of fuel prices. Fabien opened an interactive python shell and did something like:
>>> import math
>>> math.pow(2, 64)
1.8446744073709552e+19
The question was dismissed and we went on to the next question.
> A value with the last Nth digits changed.
What exactly changes? Can you compare the number entered and retrieved?
Cheers, Janik
On 10/23/24 15:32, Rolando Pérez Rebollo wrote:
Hello, when trying to input very large numbers (with no decimals, 19 digits in my specific case) in credit or debit fields from journal items these numbers are changed on saving automatically with no explanation. The issue is easily reproducible in runbot Odoo 16 CE. I think a similar issue has been reported on github (https://github.com/odoo/odoo/issues/82597).
Steps to reproduce (from a user with full accounting features enabled), demo db from runbot.com 16.0 CE:
- Go to Invoicing/Accounting/Journal Entries
- Create a new one
- In Journal Items add a new line like this:

- When saved we get:
A value with the last Nth digits changed.
I was able to debug in a local environment and my observations are:
Is not a problem from UI: emulating the creation of journal items from code gets the same results.
Is not a problem of visualization: wrong values are persisted into database.
At ORM level the large numbers are represented in python scientific notation, in this case 1.51337248356932e+18
From there python float "features" begin to work and the float part of the scientific notation gets transformed due to the way python stores float numbers.
If my tests are not wrong every single float field in Odoo is hit by this.
I think is rare nobody has notice this before. Maybe I'm ignoring some very basic fact about currency settings in Odoo that's why I'm reaching U for help or any creative idea.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- 
We are hiring: https://www.mint-system.ch/jobs
Send application to: jobs@mint-system.ch
 
CTO Mint System GmbH 
Tel: +41 44 244 7222
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by johan - 04:51 - 23 Oct 2024

Re: Big number changed automatically on float fields

> I'm interested in the business context of this problem. What kind of accounting are you doing where numbers have 19 digits?

It's a country with a very high inflation but the company operations really runs in USD so when converting from USD to local currency there are these kind of large numbers.

> A value with the last Nth digits changed.

For 1513372483569320000 is always the last five digits, the number stays the same till 15133724835693. My guess is due to the use of float for scientific notation the rest of the number gets messed up for some sort of global digit precision setting.

The columns in postgres that stores the values for credit and debit fields are of type numeric but without precision and scale settings. For me the responsible for the issue is python.

On 10/23/24 10:12, Janik von Rotz wrote:

Hi Rolando

I'm interested in the business context of this problem. What kind of accounting are you doing where numbers have 19 digits?

Your questions reminds me of the first Odoo Partner Days. Somebody asked something similar in the context of fuel prices. Fabien opened an interactive python shell and did something like:

>>> import math
>>> math.pow(2, 64)
1.8446744073709552e+19

The question was dismissed and we went on to the next question.

> A value with the last Nth digits changed.

What exactly changes? Can you compare the number entered and retrieved?

Cheers, Janik

On 10/23/24 15:32, Rolando Pérez Rebollo wrote:

Hello, when trying to input very large numbers (with no decimals, 19 digits in my specific case) in credit or debit fields from journal items these numbers are changed on saving automatically with no explanation. The issue is easily reproducible in runbot Odoo 16 CE. I think a similar issue has been reported on github (https://github.com/odoo/odoo/issues/82597).

Steps to reproduce (from a user with full accounting features enabled), demo db from runbot.com 16.0 CE:

- Go to Invoicing/Accounting/Journal Entries

- Create a new one

- In Journal Items add a new line like this:

- When saved we get:

A value with the last Nth digits changed.

I was able to debug in a local environment and my observations are:

Is not a problem from UI: emulating the creation of journal items from code gets the same results.

Is not a problem of visualization: wrong values are persisted into database.

At ORM level the large numbers are represented in python scientific notation, in this case 1.51337248356932e+18

From there python float "features" begin to work and the float part of the scientific notation gets transformed due to the way python stores float numbers.

If my tests are not wrong every single float field in Odoo is hit by this.

I think is rare nobody has notice this before. Maybe I'm ignoring some very basic fact about currency settings in Odoo that's why I'm reaching U for help or any creative idea.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- 
We are hiring: https://www.mint-system.ch/jobs
Send application to: jobs@mint-system.ch

CTO Mint System GmbH 
Tel: +41 44 244 7222
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Ing. Rolando Pérez Rebollo - 04:41 - 23 Oct 2024

Re: Big number changed automatically on float fields

https://docs.python.org/3/tutorial/floatingpoint.html


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

by Holger Brunn - 04:35 - 23 Oct 2024

1 attachments 1 attachments

Re: Big number changed automatically on float fields

That is the right question - what problem are you trying to solve that requires 19 digit numbers.

On the actual problem, this is how floating point numbers are designed to work at a low level, on Python and computers in general.
Floating point numbers don't store all the number's digits.
For efficiency they only store a limited number of "precision" digits (the ones you can see on the scientific representation) and then the power of 10 scale - where the ("floating") decimal point is.
So for very large number, you lose precision on the rightmost digits of your number.

/Daniel

On 23/10/2024 15:12, Janik von Rotz wrote:

Hi Rolando

I'm interested in the business context of this problem. What kind of accounting are you doing where numbers have 19 digits?

Your questions reminds me of the first Odoo Partner Days. Somebody asked something similar in the context of fuel prices. Fabien opened an interactive python shell and did something like:

>>> import math
>>> math.pow(2, 64)
1.8446744073709552e+19

The question was dismissed and we went on to the next question.

> A value with the last Nth digits changed.

What exactly changes? Can you compare the number entered and retrieved?

Cheers, Janik

On 10/23/24 15:32, Rolando Pérez Rebollo wrote:

Hello, when trying to input very large numbers (with no decimals, 19 digits in my specific case) in credit or debit fields from journal items these numbers are changed on saving automatically with no explanation. The issue is easily reproducible in runbot Odoo 16 CE. I think a similar issue has been reported on github (https://github.com/odoo/odoo/issues/82597).

Steps to reproduce (from a user with full accounting features enabled), demo db from runbot.com 16.0 CE:

- Go to Invoicing/Accounting/Journal Entries

- Create a new one

- In Journal Items add a new line like this:

- When saved we get:

A value with the last Nth digits changed.

I was able to debug in a local environment and my observations are:

Is not a problem from UI: emulating the creation of journal items from code gets the same results.

Is not a problem of visualization: wrong values are persisted into database.

At ORM level the large numbers are represented in python scientific notation, in this case 1.51337248356932e+18

From there python float "features" begin to work and the float part of the scientific notation gets transformed due to the way python stores float numbers.

If my tests are not wrong every single float field in Odoo is hit by this.

I think is rare nobody has notice this before. Maybe I'm ignoring some very basic fact about currency settings in Odoo that's why I'm reaching U for help or any creative idea.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- 
We are hiring: https://www.mint-system.ch/jobs
Send application to: jobs@mint-system.ch

CTO Mint System GmbH 
Tel: +41 44 244 7222
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

DANIEL REIS
MANAGING PARTNER

>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

by Daniel Reis - 04:26 - 23 Oct 2024

Re: Big number changed automatically on float fields

Hi Rolando

I'm interested in the business context of this problem. What kind of accounting are you doing where numbers have 19 digits?

Your questions reminds me of the first Odoo Partner Days. Somebody asked something similar in the context of fuel prices. Fabien opened an interactive python shell and did something like:

>>> import math
>>> math.pow(2, 64)
1.8446744073709552e+19

The question was dismissed and we went on to the next question.

> A value with the last Nth digits changed.

What exactly changes? Can you compare the number entered and retrieved?

Cheers, Janik

On 10/23/24 15:32, Rolando Pérez Rebollo wrote:

Hello, when trying to input very large numbers (with no decimals, 19 digits in my specific case) in credit or debit fields from journal items these numbers are changed on saving automatically with no explanation. The issue is easily reproducible in runbot Odoo 16 CE. I think a similar issue has been reported on github (https://github.com/odoo/odoo/issues/82597).

Steps to reproduce (from a user with full accounting features enabled), demo db from runbot.com 16.0 CE:

- Go to Invoicing/Accounting/Journal Entries

- Create a new one

- In Journal Items add a new line like this:

- When saved we get:

A value with the last Nth digits changed.

I was able to debug in a local environment and my observations are:

Is not a problem from UI: emulating the creation of journal items from code gets the same results.

Is not a problem of visualization: wrong values are persisted into database.

At ORM level the large numbers are represented in python scientific notation, in this case 1.51337248356932e+18

From there python float "features" begin to work and the float part of the scientific notation gets transformed due to the way python stores float numbers.

If my tests are not wrong every single float field in Odoo is hit by this.

I think is rare nobody has notice this before. Maybe I'm ignoring some very basic fact about currency settings in Odoo that's why I'm reaching U for help or any creative idea.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

-- 
We are hiring: https://www.mint-system.ch/jobs
Send application to: jobs@mint-system.ch

CTO Mint System GmbH 
Tel: +41 44 244 7222

by Janik von Rotz - 04:11 - 23 Oct 2024

Big number changed automatically on float fields

Hello, when trying to input very large numbers (with no decimals, 19 digits in my specific case) in credit or debit fields from journal items these numbers are changed on saving automatically with no explanation. The issue is easily reproducible in runbot Odoo 16 CE. I think a similar issue has been reported on github (https://github.com/odoo/odoo/issues/82597).

Steps to reproduce (from a user with full accounting features enabled), demo db from runbot.com 16.0 CE:

- Go to Invoicing/Accounting/Journal Entries

- Create a new one

- In Journal Items add a new line like this:

- When saved we get:

A value with the last Nth digits changed.

I was able to debug in a local environment and my observations are:

Is not a problem from UI: emulating the creation of journal items from code gets the same results.
Is not a problem of visualization: wrong values are persisted into database.
At ORM level the large numbers are represented in python scientific notation, in this case 1.51337248356932e+18

From there python float "features" begin to work and the float part of the scientific notation gets transformed due to the way python stores float numbers.

If my tests are not wrong every single float field in Odoo is hit by this.

I think is rare nobody has notice this before. Maybe I'm ignoring some very basic fact about currency settings in Odoo that's why I'm reaching U for help or any creative idea.

by Ing. Rolando Pérez Rebollo - 03:30 - 23 Oct 2024

2 attachments 2 attachments

Re: Submmit an Odoo website form as an Iframe

OK, I changed the csrf=False in another controller and then it works.

On Wed, 23 Oct 2024 at 14:36, Hed Shefer <hed@laylinetech.com> wrote:

Hi all,

I'm trying to embed an Odoo website form as an iframe and encountering a 400 error.
The original Odoo website form works well when not used in Iframe.

Tried to change csrf=False with no success, do you have other ideas?
--

--

by Hed Shefer - 01:56 - 23 Oct 2024

Submmit an Odoo website form as an Iframe

Hi all,

I'm trying to embed an Odoo website form as an iframe and encountering a 400 error.
The original Odoo website form works well when not used in Iframe.

Tried to change csrf=False with no success, do you have other ideas?

--

by Hed Shefer - 01:41 - 23 Oct 2024

My Application for OCA Delegate

Dear Delegates,

Unfortunately, I won't be able to attend tomorrow's live session. The reason is quite simple: three kids to manage at that time! :-) Wednesday is the day I dedicate to my children.

However, this does not diminish my motivation to become an OCA delegate. In fact, I have already served as a delegate in the past, until 2018, when I took a few years to focus on other professional activities.

For me, the OCA is the central and essential player in the Odoo community. We play a crucial role in enhancing and enriching Odoo's open-source ecosystem by offering a vast collection of open-source addons across many functional areas. Addons provided by the OCA offer solutions that go beyond the standard capabilities of Odoo, enabling us to meet specific client needs and further optimize their business processes. Additionally, we benefit from synergies with other stakeholders facing similar challenges or requirements.

It is for these reasons that I wish to continue promoting our work by becoming an OCA delegate once again, because together, we can take Odoo to the next level.

See you soon,

Adrien

--

Adrien Peiffer

Manager | Project & Technical Lead

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Zone industrielle 22 | L-8287 Kehlen | Luxembourg

Absent on Wednesdays

by Adrien Peiffer - 08:31 - 22 Oct 2024

Re: Scanner HW for stock_barcodes (OCA/stock-logistics-barcode)

Thank you very much for the info!
Time to order one and start tweaking it! :)


-- 
Houzéfa Abbasbhay
XCG Consulting / Ọrbeet

by Houzéfa Abbasbhay - 05:11 - 22 Oct 2024

Re: Scanner HW for stock_barcodes (OCA/stock-logistics-barcode)

It's basically the same, as the JS recognizing that a keyboard input is a barcode reading is the same (and it's based on the times, assuming that you are not able to type on that speed).

Any HW reader you buy, you will have to check for some config about the speed rate, barcode termination (avoiding extra line feeds and so on), and other tweaks, but mostly every device out there may serve.

Regards.

by Pedro M. Baeza - 05:02 - 22 Oct 2024

Scanner HW for stock_barcodes (OCA/stock-logistics-barcode)

Hi I have been playing with this great stock_barcodes module on runboat:
https://github.com/OCA/stock-logistics-barcode/tree/15.0/stock_barcodes

Been testing barcode input with xdotool on Linux; works fine for simple tests.
(More info about it in the "bar code scanner simulator" discussion from March 2020 in this mailing list.)

My question to people using this module - do you have specific scanner hardware you would recommend?

I notice the module has a dependency on barcodes from Odoo Community, which implements scanning interface here.
Odoo itself recommends hardware here and here, but I'm not sure if that applies to Odoo Community or Enterprise only.

Our OCA module also seems to implement such a scanning interface here, and without importing elements from that barcodes module (from what I can see on a cursory glance)?
Hence my question - should I follow Odoo's scanner HW recommendation, or is our interface slightly different?

Thanks for your input

-- 
Houzéfa Abbasbhay
XCG Consulting / Ọrbeet

by Houzéfa Abbasbhay - 04:56 - 22 Oct 2024

Re: Help promoting the OCA

Jordan & everyone else:

that's purely my opinion which is probably coming from me being used to this mailing list as rather technical one. I am not in a position to rule over this and if everybody else is OK with it I do not mind.

Sorry, if I overstepped. Best regards

Radovan

On utorok 22. októbra 2024 14:07:09 CEST Jordan Kinsella wrote:

> Hi Radovan,

>

> Thanks for your email. Noted.

>

> Habit, but fault. While, I disagree with your point entirely, for ease of

> argument, I will refrain in the future.

>

> Thanks, have a good week.

>

> Kind regards,

>

> None [1]

>

> *Jordan Kinsella*

> Head of Marketing | Gravitai

>

> jordan@gravitai.com | [2] +44 (0) 1233 801

> 330

> 314 Regents Park Road, Finchley,

> London N3 2LT [3]

> www.gravitai.com [4]

>

> Support |

> [5] hello@gravitai.com [6]

>

> ----

>

> CONFIDENTIAL: Within this email, any files transmitted with it are

> confidential and intended solely for the use of the individual or entity to

> whom they are addressed. If you have received this email in error, please

> notify the sender. This message contains confidential information and is

> intended only for the individual(s) named. If you are not the named

> addressee, you should not disclose, distribute or copy this email. Please

> notify the sender immediately by email if you have received this email by

> mistake and delete this email from your system. If you are not the intended

> recipient, you are notified that disclosing, copying, distributing or

> taking any action in reliance on the contents of this information is

> strictly prohibited. For more information on how we operate and deal with

> your data, please visit our website to have a look at our Privacy Policy

> [7] and

> Terms & Conditions [8] pages.

>

> WARNING: Whilst we run antivirus software on all internet emails, we are not

> liable for any loss or damage. The recipient is advised to run their own

> antivirus software while operating and viewing emails directed at them from

> Gravitai.

>

> *From:* Radovan Skolnik <notifications@odoo-community.org>

> *Sent:* 22 October 2024 12:47

> *To:* Contributors <contributors@odoo-community.org>

> *Subject:* Re: Help promoting the OCA

>

> Caution: This is an external email. Please take care when clicking links or

> opening attachments. When in doubt, contact your Department Manager

>

> Jordan,

>

> while I like your enthusiasm I would ask you (if there's not a opposite

> opinion) not to add reactions to mailing lists - this is not Facebook or

> LinkedIn. It pollutes the mailing list with emails that really do not bring

> any additional value. This is a sample of the last one that was sent to all

> subscribers:

>

> Hope you understand. Thank you.

>

> Best regards

>

> Radovan Skolnik

>

> On utorok 22. októbra 2024 12:13:08 CEST Jordan Kinsella wrote:

> > Jordan Kinsella

> > reacted to your message:

> >

> > *From:* Michel Stroom <notifications@odoo-community.org>

> > *Sent:* Tuesday, October 22, 2024 9:52:38 AM

> > *To:* Contributors <contributors@odoo-community.org>

> > *Subject:* Help promoting the OCA

> >

> > Caution: This is an external email. Please take care when clicking links

> > or

> > opening attachments. When in doubt, contact your Department Manager

> >

> > Hi OCA members and fellow Odooers,

> >

> > I wasn’t able to attend the recent OCA Days in Liège, so I began watching

> > the videos online. One of them highlighted the need for more OCA members.

> >

> > Since then, I’ve made it a daily routine to watch one OCA video each

> > morning and share my thoughts on LinkedIn, encouraging readers to

> > consider applying for membership.

> >

> > This morning, I posted Gonzalo Ruzafa talk, "How to Sell an Odoo Project."

> > In my opinion, it’s a must-see for anyone involved in selling Odoo.

> >

> > Read my latest post on LinkedIn and click the link below:

> > https://tinyurl.com/ytndcmst

> >

> > I hope this inspires more people to write about the OCA.

> > Feel free to reach out if you need help creating content.

> >

> > Best regards,

> >

> > Michel Stroom

> > LinkedIn: https://linkedin.com/in/stroom

> >

> > _______________________________________________

> > Mailing-List:

> > https://odoo-community.org/groups/contributors-15 [1]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe:

> > https://odoo-community.org/groups?unsubscribe [2]

> >

> > _______________________________________________

> > Mailing-List: https://odoo-community.org/groups/contributors-15 [3]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [4]

> >

> > [1] https://odoo-community.org/groups/contributors-15

> > [2] https://odoo-community.org/groups?unsubscribe

> > [3] https://odoo-community.org/groups/contributors-15

> > [4] https://odoo-community.org/groups?unsubscribe

>

> _______________________________________________

> Mailing-List:

> https://odoo-community.org/groups/contributors-15 [9]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe:

> https://odoo-community.org/groups?unsubscribe [10]

>

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [11]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [12]

>

> [1] https://www.gravitai.com/r/i5p

> [2] mailto:jordan@gravitai.com

> [3] https://www.gravitai.com/contact-us

> [4] https://www.gravitai.com

> [5] https://www.gravitai.com/contact-us

> [6] mailto:hello@gravitai.com

> [7] https://www.gravitai.com/privacy-policy

> [8] https://www.gravitai.com/terms-and-conditions

> [9] https://odoo-community.org/groups/contributors-15

> [10] https://odoo-community.org/groups?unsubscribe

> [11] https://odoo-community.org/groups/contributors-15

> [12] https://odoo-community.org/groups?unsubscribe

by Radovan Skolnik - 03:46 - 22 Oct 2024

Archives

Contributors

IDP initiate with SAML

Re: recurring payments

recurring payments

Global Online Candidates OCA Delegates - Dating Show

Re: Submmit an Odoo website form as an Iframe

Re: Big number changed automatically on float fields

Re: Submmit an Odoo website form as an Iframe

RE: Big number changed automatically on float fields

Re: Big number changed automatically on float fields

Re: Big number changed automatically on float fields

Re: Big number changed automatically on float fields

Re: Big number changed automatically on float fields

Big number changed automatically on float fields

Re: Submmit an Odoo website form as an Iframe

Submmit an Odoo website form as an Iframe

My Application for OCA Delegate

Re: Scanner HW for stock_barcodes (OCA/stock-logistics-barcode)

Re: Scanner HW for stock_barcodes (OCA/stock-logistics-barcode)

Scanner HW for stock_barcodes (OCA/stock-logistics-barcode)

Re: Help promoting the OCA

Follow us