← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 704191] Re: [6.0rc2] Record Modified dialog raised without modification.

 

Hello Martin,

The issue that you stated above does not occur, but there is an issue
that if you have a default datetime field set to a value with isoformat
and when the field is required. then when you try to save the form the
field will clear out. The reason is stated below:

You are passing the default value in isoformat. right ? which is say
something like '2011-01-18T16:14:58.172477' now the client expects the
datetime format as specified in your Language settings. i.e from
administration/Translations/Languages which has the format '%m/%d/%Y
%H:%M:%S' for 'en_US'. now when the client tries to parse the input
value according to the format specified in language setting. It raises
an exception like " time data '2011-01-18T16:14:58.172477' does not
match format '%m/%d/%Y %H:%M:%S' " because your input value is not in
the format that is required. Try changing the format from
Administration/Translations/Language and everything should be fine.


Thanks


** Changed in: openobject-client
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/704191

Title:
  [6.0rc2] Record Modified dialog raised without modification.

Status in OpenObject GTK Client:
  Invalid

Bug description:
  Similar to https://bugs.launchpad.net/openobject-client/+bug/703712
  but different I think.

  I had some datetime fields set by datetime.datetime.now().isoformat(' '). These would cause the 'This record has been modified do you want to save it?' dialog to pop up even when nothing had been changed.
  I changed isoformat() to strftime() and the problem went away.
  It seems the fractional seconds that isoformat() adds is causing a rounding error or something in the code that checks for modification. I don't need the fractions myself but I guess someone somewhere will.

  It took me far too long just to find which fields were at fault. It
  would be nice to be told which fields have changed in the dialog like
  in Koo (which no longer works with trunk). Maybe a 'show details' type
  thing.





References