Skip to main content
Question

tstamp cannot be empty

  • September 16, 2024
  • 5 replies
  • 71 views

We come from a version update to 2023R2, and in tables like the original acumatica PREmployeeDeduct, when updating it the following error appears, which did not happen in the previous version 2021R1, for the migration we logically made 2 jumps, the database is in sql server 2017, please have any clue

 

PD. I've checked other posts, but I can't find any clues.

5 replies

Laura02
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3132 replies
  • September 16, 2024

Hello @gparrales50 ,

I know you checked other posts, but which posts did you try?

 

The following post answered by Naveen has a solution that worked for other people.  Please confirm whether you added the  ConvertZeroDateTime=True in the web.config → Connection String as recommended by @Naveen Boga :

https://community.acumatica.com/develop%2Dcustomizations%2D288/error%2Din%2Dtstamp%2Dfield%2Dwhen%2Dsaving%2Drecords%2D16939

 

(The previous post is MySQL:  Naveen or another clever developer will need to help us figure out whether the same answer could apply to SQL Server.)

Laura


SoniaEchols90
Acumatica Moderator
Forum|alt.badge.img+1
  • Acumatica Moderator
  • 122 replies
  • September 16, 2024

gparrales50,

Not my area of expertise.  Looking at similar issues, things to try.

  • Make sure the description is not empty.
  • Make sure Year is populated and correct

If those fail, recommend you open a case with Support.


  • Author
  • Freshman II
  • 6 replies
  • September 16, 2024
Laura02 wrote:

Hello @gparrales50 ,

I know you checked other posts, but which posts did you try?

 

The following post answered by Naveen has a solution that worked for other people.  Please confirm whether you added the  ConvertZeroDateTime=True in the web.config → Connection String as recommended by @Naveen Boga :

https://community.acumatica.com/develop%2Dcustomizations%2D288/error%2Din%2Dtstamp%2Dfield%2Dwhen%2Dsaving%2Drecords%2D16939

 

(The previous post is MySQL:  Naveen or another clever developer will need to help us figure out whether the same answer could apply to SQL Server.)

Laura

Hi Laura,
I'm using Sql Server, the recommendation is for MySql.
Thank you for the suggestion.


  • Author
  • Freshman II
  • 6 replies
  • September 16, 2024
SoniaEchols90 wrote:

gparrales50,

Not my area of expertise.  Looking at similar issues, things to try.

  • Make sure the description is not empty.
  • Make sure Year is populated and correct

If those fail, recommend you open a case with Support.

Hi Sonia,

I have indeed opened the case, although I still have no response.
Thank you for the suggestion.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2751 replies
  • November 13, 2024

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


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