We have been working on this mobile error for a while, you know the type, really descriptive.
There was an error with this field's customized event.
Field: nothing there
Event: nothing there
Error: Script error
Okay. So it is somewhere in the script. Appreciate the narrowing down.
The error occurred only on the iPhone when loading the opportunity form or when creating or updating items in a custom product entity being used in a sub-grid on the opportunity form. We were able to narrow it down to a script created to update a custom estimated revenue field on the opportunity but that was as far as we could get. We could not make major modifications to the script because the web client users enjoyed the benefits of a previous performance and functionality update we had done. We were not getting the error when testing the mobile client on the Surface but we were not getting a consistently correct total either.
Finally the low tech "alerts in the code" method was employed in an attempt to figure out where the choke point was. Things like alert("Inside the new_TotalAmt here"); and alert("Just figured out the total. Next we are going to the GetProds func"); so we could see where the mobile app was choking. An interesting level of complication was added when comparing the alerts on the web client to the ones on the mobile to see where it was having an issue. We had to take pictures of the mobile alerts and then view them backwards because the mobile client produces them without stopping whereas the web client goes through one at a time, only moving to the next alert on clicking Ok to the current alert.
We checked to see if the second field was on the form, it was. Then we checked if it was available to the mobile client, it was NOT, and we checked if it was visible, it was NOT. We updated the field and moved it to our Admin tab on the form. A useful area at the bottom of any form suitable for any field not needed by the typical user but invaluable when troubleshooting.
With cautious optimism we downloaded the customizations to the mobile client, opened an opportunity, got… only alerts! Once we took the alerts away the custom code worked like a champion and everyone did their happy dance.
So the moral of this story - make sure all fields needed by your mobile client are:
1. On the form
2. Set to Visible by Default
3. Set to Available on the phone
If you pay attention to these three thing, you will save yourself a lot of time and heart ache. Maybe the heart ache is just me, but definitely a lot of time.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.