Skip to main content
Solved

Acumatica Picking wrong Location details in Appointments.


Michael Ndungi
Varsity I
Forum|alt.badge.img

Hello Everyone,
 

On appointments screen, the system picks location of when the user using the mobile device logged in the system instead of the exact location and time when the appointment was started.

 

The system always picks the first location recorded on the location Tracking history GI as shown below.


 

The system should not be picking the location of the first time the user logged in the system. 

what could be causing this issue, why does it pick the first row always for the start and End location.
Kindly assist.

Any kind of response will be highly appreciated.

Best answer by Anacarina Calvo

@development93 
To clarify, the time is based on the Actual Start Time and Actual Complete Time on the Settings tab, not the Start Time/End Time on the Log tab, although depending on the Service Order Type they could be the same. If they are the same, then as you indicate, the latitude and longitude should be the one at 10:41am and a case should be created. 

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

Anacarina Calvo
Pro I
Forum|alt.badge.img+4

Hi @development93 
The system should take the Location from the Location Tracking History form, which is earlier in time from the time in which the employee started the appointment. So for example, in your image, if the employee started at 9:15am, then the system should take the location recorder at 9:13am. 
Verify that the Actual Start Time of the Appointment is between 8:10am and 8:19am, If it is not the case, please create a case. 


Michael Ndungi
Varsity I
Forum|alt.badge.img
Anacarina Calvo wrote:

Hi @development93 
The system should take the Location from the Location Tracking History form, which is earlier in time from the time in which the employee started the appointment. So for example, in your image, if the employee started at 9:15am, then the system should take the location recorder at 9:13am. 
Verify that the Actual Start Time of the Appointment is between 8:10am and 8:19am, If it is not the case, please create a case. 

Okay, checking on this.
And just a clarification.

Should these locations be related to a certain route?

 

 


Anacarina Calvo
Pro I
Forum|alt.badge.img+4

@development93 

They are not related to a route. I will ask documentation team to fix it. Thanks!  


Michael Ndungi
Varsity I
Forum|alt.badge.img
Anacarina Calvo wrote:

Hi @development93 
The system should take the Location from the Location Tracking History form, which is earlier in time from the time in which the employee started the appointment. So for example, in your image, if the employee started at 9:15am, then the system should take the location recorder at 9:13am. 
Verify that the Actual Start Time of the Appointment is between 8:10am and 8:19am, If it is not the case, please create a case. 

Here is an example of how the system is picking the locations.

 

The system picked the values on the first row and not the locations corresponding to the start time which is 11:10
 

 


Anacarina Calvo
Pro I
Forum|alt.badge.img+4

@development93 
To clarify, the time is based on the Actual Start Time and Actual Complete Time on the Settings tab, not the Start Time/End Time on the Log tab, although depending on the Service Order Type they could be the same. If they are the same, then as you indicate, the latitude and longitude should be the one at 10:41am and a case should be created. 


Michael Ndungi
Varsity I
Forum|alt.badge.img
Anacarina Calvo wrote:

@development93 
To clarify, the time is based on the Actual Start Time and Actual Complete Time on the Settings tab, not the Start Time/End Time on the Log tab, although depending on the Service Order Type they could be the same. If they are the same, then as you indicate, the latitude and longitude should be the one at 10:41am and a case should be created. 

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