Since upgrading to ServiceMax Spring 16 on the iPads our technicians are experiencing the following error whenever they add labour to a work order.
Record Type ID: id value of incorrect type: Usage/Consumption
This causes a sync conflict and the only way it can be resolved is to remove the labour item.
In ServiceMax Summer 15 it works fine.
In our case it turned out to be a custom field we had added (Product Type) has now been added to ServiceMax as a built-in field. The two, same named fields, were conflicting.
So it could be worthwhile checking any your custom fields and see if they've been added into Spring '16 as built-in fields with the same name.
How can they conflict ? Fields added by ServiceMax are added to their Salesforce managed package(s) : does the iPad sync engine use the fielf Nam instead of the field DeveloperName ?