A client screen (e.g. Customer Info) throws an internal error like 'PLSQLEnumeration.Unpack... Number of DB values do not match the number of CLIENT values' for an enumeration used on that screen, appearing consistently on a newly-built/cloned system, even after re-cloning the database multiple times.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check for a custom enumeration value that was added to the database but never approved/published — a mismatch between how many values exist in the database for an enumeration and how many the client expects is a classic symptom of an enumeration change that was made directly in the database without going through the proper approve-and-publish step. Approving and publishing the pending enumeration change resolves the DB-vs-client value-count mismatch causing this error.

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