You can use the 'general condition' and then either make a custom macro method to specifically validate your field, or you could write a rather complicated macro expression to ensure correct validation. I think, that writing the macro in C# and then being able to debug it in VS if easier and probably more efficient. But bot is possible.
If your macro expression doesn't work, you and you don't know why you can enable macro debug in settings and then refer to macro debug in the Debug app. It does not debug the C# code of the macro, but shows the evaluation steps with the results.