A read-only Select-statement custom field on a standard Logical Unit throws an error, and the fix turns out to involve a completely different, already-Approved view under that same LU's Approved Detail Views list — why would an unrelated approved view cause this?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check the Custom Fields window for the affected LU's Approved Detail Views list — if a specific view there (unrelated to the one your new custom field's select statement actually needs) is currently in Approved state, right-click it and choose Disapprove. An approved detail view that overlaps or conflicts with what your custom field's select statement is trying to do can cause errors that look unrelated to your actual field; disapproving the conflicting view (rather than the one you actually need) has resolved this in confirmed cases, without needing to change your custom field's own definition 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