The custom field configuration links (e.g. for default value, options) on the ConfigureCustomField action always use the id of the fieldconfigscheme for both the fieldconfigscheme and the fieldconfiguration parameters. If the tables fieldconfigscheme and fieldconfiguration are not id-matched for each custom field, this can lead to unexpected results such as configuring the wrong field or a 500 page caused by a null pointer exception.

There is no known way the data can become inconsistent in this way except by direct modification of the database, but there is no data integrity violation and the link is clearly wrong.

The error is in the expression on line 70 of configurecustomfield.jsp where the id for the fieldconfiguration should be given the value of "../key/id". Instead it doesn't resolve (as "../id" so Webwork (in its wisdom) walks up the value stack and finds the fieldconfigscheme id which just happens to be the correct value for the fieldconfiguration id in all normal cases. One case where it is not the same is in the example provided for JSP-7492 where there is something strange in the data making the ids of those two tables unaligned.