Why doesn't a custom-field view like a `_pub_cfv` view hold the same custom fields already added to the corresponding plain `_cfv` view for what seems like the same underlying data, and how are these `_pub`-suffixed views actually generated?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

These are two genuinely different standard views, not two names for the same thing — the _pub-suffixed view and the plain view are connected to two separate standard views (commonly used by two different IFS screens for their own distinct purposes), so custom fields added to one don't automatically appear on the other. Alternate view suffixes like _UIV, _PUB, _BI, _LOV, and _LIST aren't automatically or mechanically generated variants of a base view at all — they're deliberately created by IFS's own developers for specific distinct purposes. Custom fields need to be added separately to whichever specific view(s) the screen(s) you actually care about are genuinely built on, rather than assuming a _pub-suffixed view will automatically inherit fields added to its plain counterpart.

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

← Browse Developer Studio, deployment, and upgrades questions