Method:Classic General Q&A

Re: Mobile Screen Error Messages

Innovative — Wed, 06 Jul 2011 17:35:00 GMT

all appears to be working again now, it is a custom screen but what ever fix was dobe resolved it

thks

Re: Mobile Screen Error Messages

Method_Michael — Wed, 06 Jul 2011 15:38:56 GMT

Innovative,

Innovative:
I am still having issues with mobile screens it is leaving the cost of item blank in the grid and leaving the description blank

What screen is this happening on? Is it a customized screen or a standard screen? Does the same thing happen on the standard screen,?

Innovative:
When completing the work order it is leaving the invoice status blank as well which is a new issue.

I just tried this on the standard Mobile Work Order screen and it worked fine, is there any other specifics you can give me?

-Michael

Re: Mobile Screen Error Messages

Innovative — Wed, 06 Jul 2011 15:22:05 GMT

Michael

I am still having issues with mobile screens it is leaving the cost of item blank in the grid and leaving the description blank. When completing the work order it is leaving the invoice status blank as well which is a new issue. I assume there has been a platform update later last week?

Re: Mobile Screen Error Messages

Method_Michael — Wed, 06 Jul 2011 14:49:56 GMT

Steven,

This should no longer be an issue, let me know if that is not the case.

-Michael

Re: Mobile Screen Error Messages

Steven — Tue, 05 Jul 2011 22:01:04 GMT

Michael,

We currently have twenty crews not able to clock in and out from the mobile device. Since they are unable to clock in and out we are entering the time manually. Have you been able to find out why the error is occuring?

Re: Mobile Screen Error Messages

Method_Michael — Tue, 05 Jul 2011 16:00:21 GMT

Hi Steven,

I was able to duplicate this issue. Let me look into this further.

-Michael

Mobile Screen Error Messages

Steven — Tue, 05 Jul 2011 15:17:56 GMT

An error message is popping up when our foremen open jobs in the mobile work order list screen that states "undefined". Also, the start/end dates are blank causing another error message when the user tries to clock in/out of a job.

Any suggestions on how to fix this?