There are two things about validateField, that I haven't been able to figure out:
- Is the method originally intended to be called only when a field value is changed, or should you also be able to call it to validate the current value?
- Why do AX 2012 also have a name based validateFieldValue method?
I raise the first question because the standard AX data consistency check actually calls validateField on existing data to check the present value of the fields. That gives a number of errors from standard AX, that really isn't errors but appears so because the code on the field assumes you have modified the field value from something else to the present value.
One example of this, is the many errors you get from Currency:
In this case you could add code to see if the value actually is changed.
Also some validations should check that the field actually has value. One example from standard AX of a validation not doing this is license plate validation on warehouse locations, where a blank value in some fields will give you this error:
Here the validation looks up another location using a blank value, and the returned flag for License Plate Control will of course be blank.
Don’t update data in a validation method. You should always be able to call a validation method without risking any data to change in the system. Changes should be moved to the modifiedField, modifiedFieldValue, update or insert method.
Don't display any dialogs from the table based validation method without checking if the validation method is being triggered from a form data source. The code analysis tool on LCS will report this as a Best Practice issue, as the validation could be called from a server tier. Consider moving these dialogs to the forms where needed.