A standard field that exists on the core entity (e.g. Reference No on the JT Task entity) is available to add to other pages, but doesn't show up in the field picker when configuring a Mobile screen — even though several custom fields on the same entity work fine there. Why would one specific standard field be excluded?

All FAQ questions / Mobile and service touch apps (MWO/MRO)

Answer

This is most likely by design rather than a bug — not every field that exists on the underlying database table for an entity is synced to the mobile data layer, and a field that isn't part of that mobile sync set simply won't appear as an option in the mobile Page Designer's field picker, regardless of how many custom fields on the same entity do work there. If a specific standard field you need isn't available, that's worth confirming with IFS Support as an intentional scope limitation rather than assuming it's a configuration mistake on your side.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Mobile and service touch apps (MWO/MRO) questions