Publishing a read-only custom attribute fails with "the column X referred to in table t is not an approved persistent Custom Attribute," even though X is confirmed to be a genuine standard column on the underlying table (not a custom one), visible with data when queried directly.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check whether the specific activated view being used for that entity's custom-field SQL actually exposes the column in question — custom-field validation checks against the columns the activated view exposes, not against the raw underlying table, so a standard column that's genuinely present on the table but happens to be missing from that particular activated view will trigger exactly this misleading "not an approved Custom Attribute" error, even though the column itself isn't custom at all.

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