Le 14/05/2018 à 14:51, Mayost Sharon a écrit : > Thanks > Is this corrected in version 3.11? > The fix will go in a next 3.11.3 release. Regards, -- Benoît Minisini