By default, the mobile apps show all fields even if they are set to non-visible in the Salesforce field level security (FLS) settings. If you try to update one of these fields in a SFM on mobile, once the sync is complete nothing happens and the field is not updated.
If you wish to have the mobile app to respect field level security (FLS) settings, ServiceMax provide a configuration option that you can enable. This is: SET-008 - "Skip inaccessible fields" (true/false)
However, if you enable this and a field is present in a SFM view which the user does not have access to (because of FLS), then it causes the entire view layout to go blank and ALL fields show no values. Therefore rendering this setting useless. The advice given is to remove the field from the SFM View, but then there's no point enabling SET008 in the first place.
When SET 008 is set to true, if a field is present on a SFM view or SFM update, then the app should just ignore this field only and hide it from the layout, but all other fields should still be shown.
Our main use case for this is: We have one work order SFM view that is shared across different countries, but two countries need to see an extra field on the layout that is not required for the other countries. If we can use this setting, we can keep one SFM view, but show/hide the extra field using FLS. However, because of the current way it works, we have to create two SFM views instead of one meaning there is more config to update for future changes and more complexity. Our actual use case is more complicated than this and we have to have 5x SFM's views instead of one because of this issue.
What is the underlying problem do you intend to solve with this idea?
Simplicity and flexibility of configuration.
How is the problem being addressed today, if at all?