While testing the iPhone Summer 16 app, we have found that some features and functions just do not work unless we add a certain field to the SFM view or edit SFM.
Examples of this are:
SFM Formulas don't work unless the fields they update are on the layout. We would like to set some fields in the background but can't because they have to be shown to the tech
Picklist values don't respect the record type unless the record type ID field is on the layout.
If an sfm mapping is setting a field but its not on the layout, the layout goes blank until the record is synced
Lookup context is only possible if the context field is on the layout
A translation of a pick list value will only work on a service report if the field is included on the view layout for that object and is active for the group profile. If the field is not included on the view layout, it just shows the default translation
It would be great to remove these restrictions as it would make the app more flexible, less frustrating to configure and more streamlined/user friendly to the tech.
What is the underlying problem do you intend to solve with this idea?
Ease of configuration and usability for the tech
How is the problem being addressed today, if at all?