Skip to main content
Solved

Opportunity - Incorrect datetime value: '4095-15-255 255:63:63.1048575'


Forum|alt.badge.img

Hi Team,

We are getting the below error when an update is done on CROpportunity table.

“Incorrect datetime value: '4095-15-255 255:63:63.1048575' for column 'Tstamp' at row 1

Column tststamp on the table is defined as

`tstamp` timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6), 

from my understanding this means if there is no explicit value defined for tststamp, if any update happens the value for tstamp column should be set to current timestamp. Not sure how this invalid value is getting set.

 

 

Best answer by vib1980

we did furthermore analysis from our side and found out that there was a configuration change made on our db server (sql_mode is now set to STRICT_TRANS_TABLES).

While updating Opportunity there is a section of code that selects timestamp for the graph.

 

New restriction on the DB server could be the reason why it’s failing with Incorrect datetime value: '4095-15-255 255:63:63.1048575'. There is another way to set timestamp for the graph from db using PXDatabase.SelectTimeStamp() but unsure what are the underlying impact.

 

View original
Did this topic help you find an answer to your question?

5 replies

Forum|alt.badge.img+10
  • Semi-Pro III
  • 229 replies
  • July 24, 2023

Hi @vibindas ,

Is there any customization published?

Try unpublishing the customization and check if the issue persists.

Hope, it helps!

Regards,

Sweta


Forum|alt.badge.img
  • Author
  • 69 replies
  • July 24, 2023

Hi @sweta68 , 

Yes we do have Customizations, but we are not explicitly setting any values for the timestamp field.

 

Regards,

Vibin


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2640 replies
  • August 10, 2023

Hi @vibindas were you able to find a solution? Thank you!


Forum|alt.badge.img
  • Author
  • 69 replies
  • August 10, 2023

@Chris Hackett , no luck so far.


Forum|alt.badge.img
  • Author
  • 69 replies
  • Answer
  • August 21, 2023

we did furthermore analysis from our side and found out that there was a configuration change made on our db server (sql_mode is now set to STRICT_TRANS_TABLES).

While updating Opportunity there is a section of code that selects timestamp for the graph.

 

New restriction on the DB server could be the reason why it’s failing with Incorrect datetime value: '4095-15-255 255:63:63.1048575'. There is another way to set timestamp for the graph from db using PXDatabase.SelectTimeStamp() but unsure what are the underlying impact.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings