Custom Fields added to the Base Profile become visible to all users immediately after they restart their session, but Custom Columns added to a window (like Shop Floor Workbench) and added to the same Base Profile don't show up the same way — users still have to manually RMB > Column Chooser and make each column visible themselves. Is Base Profile simply not the right mechanism for pushing out Custom Column visibility?

All FAQ questions / Platform, Aurena, and customization

Answer

Correct — Custom Columns don't propagate their visibility/layout through the Base Profile the way Custom Fields do; this is a real, confirmed difference in behavior between the two, not a configuration mistake. The working alternative: configure the custom column's visibility, size, and position exactly as needed on one reference account's own session, save that as a Personal Profile, export it, and then import that same Personal Profile onto each target user's or terminal's account — this reliably deploys the correct custom-column layout, which the Base Profile alone can't do for this particular kind of customization.

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

← Browse Platform, Aurena, and customization questions