Skip to main content
Solved

Field Service Time Entry Known issue

  • December 15, 2025
  • 2 replies
  • 23 views

dales60
Freshman I

Is anyone familiar with the know issue below and the workaround.?

I am having a hard time following this write up, please help me understand

 

 

 

AC-292726: If the Enable Time & Expenses Integration check box was selected on the Service Management Preferences (FS100100) form, and a user created logs for an appointment that were linked to a submitted or released time card or time activity before the check box was cleared, they could delete the log records manually or automatically on the Appointments (FS300200) form when they reopened the appointment.
As a result, the time entry kept the reference to the deleted log and the data was inconsistent. Also, if a user clicked Correct on the Employee Time Cards (EP305000) form for a time card that contained the deleted log, the following error message was displayed: An error occurred during processing of the field Log Ref. Nbr. value %Log Ref Nbr%. Error: Log Ref. Nbr. ‘ %Log Ref Nbr%‘ cannot be found in the system.
Workaround: Please find the workaround in this knowledge base article.

Best answer by vdiaz

@dales60 ​@ranjithduraisamy72  Hi! 

Sorry about that — bug descriptions can be pretty technical and not always reader-friendly. Here’s what it means in simpler terms:

In short:

if time was registered in an appointment (by adding Logs) that created time entries (Employee Time Cards /Employee Time Activites), and that time entry was already submitted/approved/released, then later turning Time & Expenses Integration off (on the Service Management Preferences (FS100100)), users were able to delete directly the logs or reopen the appointment (which would also can cause those log lines to be deleted). The time entry still keeps a reference to the deleted log, so the system ends up inconsistent.

Basically, it was possible to delete logs related to submitted/approved/released time activities. 

Example:

  • Technician completes an appointment → logs generate time → payroll submits/releases time card → admin disables integration and reopens appointment → logs get cleared → payroll tries to correct the time card and hits the missing log reference error.

Consequences:

  • In some cases, users were to able to correct the time cards 
  • In other cases, it was not possible to release time cards
  • Users would notice that time activities reflected entries for employees that didn’t exist in the appointments.

The link to the knowledge base article is broken, please find the link below (the workaround is basically to contact Acumatica support since a script needs to be run to correct the data corruption): 

2 replies

Forum|alt.badge.img+2

@dales60 I too experienced a same issue but unable to open the work around.


vdiaz
Acumatica Moderator
Forum|alt.badge.img+2
  • Acumatica Moderator
  • Answer
  • December 19, 2025

@dales60 ​@ranjithduraisamy72  Hi! 

Sorry about that — bug descriptions can be pretty technical and not always reader-friendly. Here’s what it means in simpler terms:

In short:

if time was registered in an appointment (by adding Logs) that created time entries (Employee Time Cards /Employee Time Activites), and that time entry was already submitted/approved/released, then later turning Time & Expenses Integration off (on the Service Management Preferences (FS100100)), users were able to delete directly the logs or reopen the appointment (which would also can cause those log lines to be deleted). The time entry still keeps a reference to the deleted log, so the system ends up inconsistent.

Basically, it was possible to delete logs related to submitted/approved/released time activities. 

Example:

  • Technician completes an appointment → logs generate time → payroll submits/releases time card → admin disables integration and reopens appointment → logs get cleared → payroll tries to correct the time card and hits the missing log reference error.

Consequences:

  • In some cases, users were to able to correct the time cards 
  • In other cases, it was not possible to release time cards
  • Users would notice that time activities reflected entries for employees that didn’t exist in the appointments.

The link to the knowledge base article is broken, please find the link below (the workaround is basically to contact Acumatica support since a script needs to be run to correct the data corruption):