Like Juhl said, just don't validate the field in your extension code, assign it.
If using a page for input, try to do the same by indirectly assigning it.
You can set a field value without validating it, which simply doesn't execute the OnValidate code. You can subscribe to OnBefore and OnAfter, and you can add code to OnValidate triggers in table extensions. Some OnValidate triggers raise event publishers that you can subscribe to in your extension.
What you cannot do is disable the OnValidate code in an extension. If BC (whether it's the base app or your extension) causes a field validation, it will always run the code in the OnValidate trigger.
That was a solution how to disable On Validate trigger but another important question and decision is - Do you really disable it and if it standard NAV field?
Answers
If using a page for input, try to do the same by indirectly assigning it.
What you cannot do is disable the OnValidate code in an extension. If BC (whether it's the base app or your extension) causes a field validation, it will always run the code in the OnValidate trigger.
RIS Plus, LLC
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/