Cause
This issue is caused during a TaroWorks 4.9 upgrade when records had previously been assigned to mobile users using a method other than directly through the TaroWorks user interface.
Solution
Please contact support@taroworks.org so they can assist you in completing your upgrade.
Comments
0 comments
Please sign in to leave a comment.